From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc,6.1?] Use right frame ID in step_over_function
Date: Sat, 06 Mar 2004 00:08:00 -0000 [thread overview]
Message-ID: <4049168B.9040508@gnu.org> (raw)
In-Reply-To: <20040305233935.GA13372@nevyn.them.org>
>>>Its pretty heavy a change to apply to that branch and this late. However,
>>>> >like Joel's related patch, I suspect it will be needed :-/
>>
>>>
>>> I've checked this into the mainline. For the moment I think I'll drop
>>> the idea of committing it to the branch.
>
>
> Since I'm not sure if you answered this already - is there a platform
> (presumably NetBSD/PPC?) on which this changes testsuite results, or
> did you just see it in using GDB on that platform?
Yes. NetBSD/PPC with a proper frame unwinder demonstrated an
improvement (but the problem wasn't NetBSD specific).
Andrew
> Anyway, great - there's a hack in the ARM sigtramp unwinder that I
> -suspect- is dead now. I'll investigate.
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc,6.1?] Use right frame ID in step_over_function
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <4049168B.9040508@gnu.org> (raw)
Message-ID: <20040319000900.y6hRFn0Foof8c0vUMAQfRcAvPGcgwMDAd2K92zadJNk@z> (raw)
In-Reply-To: <20040305233935.GA13372@nevyn.them.org>
>>>Its pretty heavy a change to apply to that branch and this late. However,
>>>> >like Joel's related patch, I suspect it will be needed :-/
>>
>>>
>>> I've checked this into the mainline. For the moment I think I'll drop
>>> the idea of committing it to the branch.
>
>
> Since I'm not sure if you answered this already - is there a platform
> (presumably NetBSD/PPC?) on which this changes testsuite results, or
> did you just see it in using GDB on that platform?
Yes. NetBSD/PPC with a proper frame unwinder demonstrated an
improvement (but the problem wasn't NetBSD specific).
Andrew
> Anyway, great - there's a hack in the ARM sigtramp unwinder that I
> -suspect- is dead now. I'll investigate.
next prev parent reply other threads:[~2004-03-06 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 4:33 Andrew Cagney
2004-02-29 17:18 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-01 1:24 ` Andrew Cagney
2004-03-05 23:02 ` Andrew Cagney
2004-03-05 23:39 ` Daniel Jacobowitz
2004-03-06 0:08 ` Andrew Cagney [this message]
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
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=4049168B.9040508@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.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