public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "kgallowa at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/3999] New: On x86_64 Frysk uses the x86_64 version of libunwind to trace 32-bit programs Date: Wed, 07 Feb 2007 21:45:00 -0000 [thread overview] Message-ID: <20070207214447.3999.kgallowa@redhat.com> (raw) Because the x86 and x86_64 versions of libunwind use different sets of registers for these architectures, the wrong values are passed to the accessreg callback. For example, when looking for the IP (RIP on 64, EIP on 32) it will still pass 16 to accessreg which corresponds to RIP on 64, but ST5 on 32. For 32, since it wants the IP, it should be passing 8, which corresponds to EIP. Because of this, it does not obtain the correct value for the IP, and the backtrace fails. To fix this, Frysk needs to check the elfclass of the binary and invoke the proper version of libunwund (libunwund-x86 for 32, libuwind-x86_64 for 64). -- Summary: On x86_64 Frysk uses the x86_64 version of libunwind to trace 32-bit programs Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: kgallowa at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3999 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-02-07 21:45 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-07 21:45 kgallowa at redhat dot com [this message] 2007-02-07 21:46 ` [Bug general/3999] " npremji at redhat dot com 2007-02-07 21:47 ` npremji at redhat dot com 2007-02-08 18:13 ` cagney at redhat dot com 2007-03-23 19:31 ` npremji at redhat dot com 2007-03-23 19:36 ` npremji at redhat 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=20070207214447.3999.kgallowa@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@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).