Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: gdb-patches@sourceware.org, Mark Kettenis <kettenis@gnu.org>,
		Michael Matz <matz@suse.de>
Subject: Re: RFC: %ebp-based backtrace patch
Date: Mon, 06 Jul 2009 20:21:00 -0000	[thread overview]
Message-ID: <20090706202103.GA9412@caradoc.them.org> (raw)
In-Reply-To: <y0mzlbhy3m8.fsf@fche.csb>

On Mon, Jul 06, 2009 at 04:10:23PM -0400, Frank Ch. Eigler wrote:
> Daniel Jacobowitz <drow@false.org> writes:
> 
> > A number of Linux distributions are carrying the attached patch from
> > Michael Matz.  [...]
> >   https://bugzilla.novell.com/show_bug.cgi?id=390722#c25
> >[...]
> > 	* i386-tdep.c (i386_frame_cache): Assume anonymous functions use
> > 	a frame pointer.
> >[...]
> 
> Could gdb partially disassemble such functions to check
> whether %ebp is likely being used as this heuristic expects?

I don't think so, but maybe someone else will come up with a way.
Since we don't know the function's start address, we could be anywhere
in the function.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-07-06 20:21 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 [this message]
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
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=20090706202103.GA9412@caradoc.them.org \
    --to=drow@false.org \
    --cc=fche@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kettenis@gnu.org \
    --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