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/14492] broken with -fPIE -pie
Date: Sun, 19 Aug 2012 07:36:00 -0000	[thread overview]
Message-ID: <bug-14492-4717-tzMpQEfgNC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14492-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14492

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING

--- Comment #8 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-08-19 07:35:57 UTC ---
When you have a frame with failed unwind (like the frame #0, as JIT code
unwinding is not supported by 'crack-language') then anything can happen.
Frames from #1 upwards are only a wild guess.  Nobody had to call strcmp in
this case, it could be leftover return address from some previous execution
(preserved due to a stack buffer) etc.

-- 
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.


  parent reply	other threads:[~2012-08-19  7:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18  8:35 [Bug backtrace/14492] New: " wbrana at gmail dot com
2012-08-18  8:51 ` [Bug backtrace/14492] " jan.kratochvil at redhat dot com
2012-08-18  9:28 ` wbrana at gmail dot com
2012-08-18 10:44 ` jan.kratochvil at redhat dot com
2012-08-18 15:39 ` vapier at gentoo dot org
2012-08-18 18:08 ` wbrana at gmail dot com
2012-08-18 18:16 ` wbrana at gmail dot com
2012-08-19  5:06 ` jan.kratochvil at redhat dot com
2012-08-19  7:24 ` wbrana at gmail dot com
2012-08-19  7:36 ` jan.kratochvil at redhat dot com [this message]
2012-08-19  9:56 ` wbrana 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-14492-4717-tzMpQEfgNC@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: link
Be 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).