public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jkain at nvidia dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug backtrace/15032] GNU/Linux backtrace fails to use eh_frame information when built with --enable-64-bit-bfd Date: Tue, 22 Jan 2013 20:26:00 -0000 [thread overview] Message-ID: <bug-15032-4717-uAFwsw6QUg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15032-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15032 --- Comment #9 from Joseph Kain <jkain at nvidia dot com> 2013-01-22 20:26:47 UTC --- I haven't done a bisect, but by code inspection/blame I found this: http://sourceware.org/git/?p=binutils.git;a=commitdiff;h=e8a3a9901149ac2fe85f11b3c8bc66cf4074b94c;hp=7093cb064f881aef599b5f12ab2b8286315bb889 Does this give you what you need? -- 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 prev parent reply other threads:[~2013-01-22 20:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-17 21:07 [Bug backtrace/15032] New: " jkain at nvidia dot com 2013-01-17 21:15 ` [Bug backtrace/15032] " jkain at nvidia dot com 2013-01-18 19:57 ` jan.kratochvil at redhat dot com 2013-01-18 20:29 ` jkain at nvidia dot com 2013-01-18 20:38 ` jan.kratochvil at redhat dot com 2013-01-18 21:25 ` jkain at nvidia dot com 2013-01-18 21:42 ` jkain at nvidia dot com 2013-01-21 18:39 ` jan.kratochvil at redhat dot com 2013-01-22 20:11 ` jkain at nvidia dot com 2013-01-22 20:18 ` jan.kratochvil at redhat dot com 2013-01-22 20:26 ` jkain at nvidia dot com [this message] 2013-01-27 17:49 ` jan.kratochvil at redhat dot com 2013-02-04 19:06 ` palves at redhat dot com 2013-02-07 18:18 ` jkain at nvidia 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-15032-4717-uAFwsw6QUg@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).