From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>,
gdb-patches@sourceware.org, matz@suse.de
Subject: Re: RFC: %ebp-based backtrace patch
Date: Sun, 27 Dec 2009 16:59:00 -0000 [thread overview]
Message-ID: <20091227165916.GA24409@caradoc.them.org> (raw)
In-Reply-To: <20090708125330.GA29881@caradoc.them.org>
On Wed, Jul 08, 2009 at 08:53:30AM -0400, Daniel Jacobowitz wrote:
> On Wed, Jul 08, 2009 at 11:01:16AM +0200, Mark Kettenis wrote:
> > Before comitting this diff, I ran the testsuite, and noticed a
> > regression. The problem is that if you do a function call through a
> > null-function-pointer or an otherwise corrupt function pointer, and
> > get a SIGSEGV, the backtrace no longer shows the frame that did the
> > function call.
> >
> > Until we come up with a way to fix this issue, I'm not going to commit
> > the diff.
>
> Hmm. if (target_read_memory (pc, buf, 1)) ? That's how a similar
> issue is handled on ARM, in arm_stub_unwind_sniffer.
Hi Mark,
I was looking through Ubuntu's local GDB patches and noticed this one
is still outstanding. Will the above work? I can test and
(hopefully) commit it, if you'd like.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-12-27 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 18:33 Daniel Jacobowitz
2009-07-06 20:11 ` Frank Ch. Eigler
2009-07-06 20:21 ` Daniel Jacobowitz
2009-07-07 12:15 ` Michael Matz
2009-07-07 13:19 ` Frank Ch. Eigler
2009-07-07 13:49 ` Michael Matz
2009-07-06 21:57 ` Mark Kettenis
2009-07-07 12:00 ` Michael Matz
2009-07-07 13:00 ` Daniel Jacobowitz
2009-07-07 13:07 ` Mark Kettenis
2009-07-08 9:01 ` Mark Kettenis
2009-07-08 12:53 ` Daniel Jacobowitz
2009-12-27 16:59 ` Daniel Jacobowitz [this message]
2009-12-27 21:37 ` Mark Kettenis
2009-12-27 22:03 ` Daniel Jacobowitz
2010-02-01 19:46 ` Daniel Jacobowitz
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=20091227165916.GA24409@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=matz@suse.de \
/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