public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug backtrace/14646] [x32] backtrace doesn't work Date: Mon, 01 Oct 2012 17:59:00 -0000 [thread overview] Message-ID: <bug-14646-4717-pLrW0xVLGX@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14646-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14646 --- Comment #9 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-10-01 17:59:26 UTC --- OK, you are right; GCC has built it as x32 but the kernel executes it as x86_64: $ file x32 x32: ELF 32-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped (gdb) disas Dump of assembler code for function f: => 0x00400094 <+0>: push %rbp [...] (gdb) p/x $sp $1 = 0xffffce20 (gdb) stepi 0x00400095 1 int f (void) { (gdb) p/x $sp $2 = 0xffffce18 -- 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:[~2012-10-01 17:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-29 18:04 [Bug backtrace/14646] New: [x32] backtrace doesn't work before main hjl.tools at gmail dot com 2012-09-29 23:25 ` [Bug backtrace/14646] " hjl.tools at gmail dot com 2012-09-30 21:16 ` hjl.tools at gmail dot com 2012-10-01 16:13 ` jan.kratochvil at redhat dot com 2012-10-01 16:31 ` [Bug backtrace/14646] [x32] backtrace doesn't work hjl.tools at gmail dot com 2012-10-01 16:55 ` jan.kratochvil at redhat dot com 2012-10-01 17:14 ` hjl.tools at gmail dot com 2012-10-01 17:20 ` jan.kratochvil at redhat dot com 2012-10-01 17:33 ` hjl.tools at gmail dot com 2012-10-01 17:59 ` jan.kratochvil at redhat dot com [this message] 2012-10-01 18:42 ` hjl.tools at gmail dot com 2012-10-15 20:37 ` cvs-commit at gcc dot gnu.org 2012-11-10 0:50 ` cvs-commit at gcc dot gnu.org 2012-11-10 0:52 ` hjl.tools at gmail 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-14646-4717-pLrW0xVLGX@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).