public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "mail at eliasprobst dot eu" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/9538] gdb creates debuginfo path incorrectly for symlinked files Date: Tue, 01 Feb 2011 21:47:00 -0000 [thread overview] Message-ID: <bug-9538-4717-hQumtCuvdy@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-9538-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=9538 Elias Probst <mail at eliasprobst dot eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mail at eliasprobst dot eu --- Comment #1 from Elias Probst <mail at eliasprobst dot eu> 2011-02-01 21:46:55 UTC --- I can confirm this behaviour. The crash happens in: /usr/lib64/dri/i965_dri.so which is a symlink to /usr/lib64/mesa/i965_dri.so The splitted debugging symbols reside in /usr/lib/debug/usr/lib64/mesa/i965_dri.so.debug GDB is only able to create backtraces when copying the debugging symbols to /usr/lib/debug/usr/lib64/dri/i965_dri.so.debug I thin the fix is actually rather simple: GDB should simply do a readlink() on the path of the file which is analyzed before looking for the corresponding debugging symbols file. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next parent reply other threads:[~2011-02-01 21:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-9538-4717@http.sourceware.org/bugzilla/> 2011-02-01 21:47 ` mail at eliasprobst dot eu [this message] 2012-01-10 20:29 ` ppluzhnikov at google dot com 2012-01-10 20:36 ` ppluzhnikov at google dot com 2012-01-18 18:59 ` cvs-commit at gcc dot gnu.org 2012-01-18 19:03 ` ppluzhnikov at google dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-9538-4717-hQumtCuvdy@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).