From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [patch, rfc, 6.0] Change frame predicates to sniffers
Date: Tue, 15 Jul 2003 17:41:00 -0000 [thread overview]
Message-ID: <3F143CC6.5060304@redhat.com> (raw)
In-Reply-To: <3F0F32C4.9060700@redhat.com>
> Hello,
>
> This patch adds frame sniffers (name stolen from other sniffer code) to the frame code. Unlike the existing frame predicate methods that take a PC parameter, these take a full NEXT_FRAME. It leaves the old frame predicates alone (making this safe for the branch).
>
> I figure that should be enough to keep any unwinder, trying to decide if the frame is good, happy :-)
>
> I'll look to commit this to both the trunk and 6.0 branch early next week. I'll then follow up with patches to:
>
> - rips out the old predicate methods (mainline only)
>
> - replace the dwarf2 predicate with a dwarf2 sniffer
> Will apply to mainline and branch. Should fix weird edge case where a function has no cfi but is doing a tail call to a no-return function, but the code following the function does have CFI.
>
> - (I guess) something to work around the dwarf2 unwind info (need to look at Mark's old code)
>
> I've so far tested it on a RH9 system (with the sniffer enabled) and it hasn't shown a sign of regressing.
>
> Can anyone point me at testcases that will magically start passing with this fixed?
I've checked this part in
Andres ;-)
next prev parent reply other threads:[~2003-07-15 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 21:57 Andrew Cagney
2003-07-15 17:41 ` Andrew Cagney [this message]
2003-07-12 19:19 Michael Elizabeth Chastain
2003-07-13 16:55 ` Mark Kettenis
2003-07-15 15:56 ` Andrew Cagney
2003-07-14 5: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=3F143CC6.5060304@redhat.com \
--to=ac131313@redhat.com \
--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