public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>, gdb@sources.redhat.com
Subject: Re: backtrace through 'sleep', (1255 and 1253)
Date: Mon, 04 Aug 2003 15:36:00 -0000	[thread overview]
Message-ID: <20030804153619.GA4738@nevyn.them.org> (raw)
In-Reply-To: <16174.32383.696875.168608@localhost.redhat.com>

On Mon, Aug 04, 2003 at 11:40:47AM -0400, Elena Zannoni wrote:
> Unlikely to happen, I am afraid :-(
> 
>  > . Ask the gcc guys directly to not schedule any instructions between
>  >   'push %ebp' and 'mov %esp, %ebp'.
>  > 
> 
> more likely.

Not very, I think.

>  > . Change gdb so that the prologue reader is more powerful.  It doesn't
>  >   take much to get through the 'xor %ecx, %ecx' instruction.  The
>  >   trouble is that there could be a billion different instructions
>  >   in there ('mov any-register, immediate').  The advantage is that
>  >   this would work without any changes to external software.
>  > 
> 
> yes. How did the prologue analyzer changed between 5.3 and now?

Mark dramatically enhanced it at the same time he added dwarf2 CFI
unwinding.  Unfortunately, the higher accuracy is causing it to assume
some functions are frameless which aren't.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-08-04 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-02 15:18 Michael Elizabeth Chastain
2003-08-04 15:33 ` Elena Zannoni
2003-08-04 15:36   ` Daniel Jacobowitz [this message]
2003-08-04 16:35 Michael Elizabeth Chastain

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=20030804153619.GA4738@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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).