From: "J. Johnston" <jjohnstn@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: ia64 patch to handle predicated insns in prologue
Date: Tue, 26 Aug 2003 22:26:00 -0000 [thread overview]
Message-ID: <3F4BDE86.6090906@redhat.com> (raw)
In-Reply-To: <1030826201050.ZM26618@localhost.localdomain>
Patch checked in, thanks. I forgot to ask: should all the ia64-tdep.c changes be
put into gdb-6.0?
-- Jeff J.
Kevin Buettner wrote:
> On Aug 26, 2:30pm, J. Johnston wrote:
>
>
>>The accompanying patch handles a bug in backtracing through glibc's sleep.
>>The compiler generates some predicated insns prior to saving the return register
>>b0 into a register stack register. The current code stops when it sees a
>>predicated insn. The change makes the prologue examination stop only if the
>>function is frameless or we have already seen the return register.
>>
>>This removes a number of failures in gdb.threads caused when we catch another
>>thread in sleep and we try and backtrace.
>>
>>Ok to commit?
>
>
> Okay.
>
> Thanks again,
>
> Kevin
>
next prev parent reply other threads:[~2003-08-26 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 19:50 J. Johnston
2003-08-26 20:10 ` Kevin Buettner
2003-08-26 22:26 ` J. Johnston [this message]
2003-08-26 22:36 ` Kevin Buettner
2003-08-27 18:26 ` J. Johnston
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=3F4BDE86.6090906@redhat.com \
--to=jjohnstn@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
/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