From: Mark Kettenis <kettenis@chello.nl>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [i386newframe/PATCH] New i386newframe branch
Date: Thu, 01 May 2003 20:54:00 -0000 [thread overview]
Message-ID: <200305011839.h41IdPdc000324@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <3EADA9AC.8030607@redhat.com> (message from Andrew Cagney on Mon, 28 Apr 2003 18:22:36 -0400)
Date: Mon, 28 Apr 2003 18:22:36 -0400
From: Andrew Cagney <ac131313@redhat.com>
> +static int
> +i386_frameless_function_invocation (struct frame_info *frame)
> {
I'd consider deleting it.
For non legacy architectures, apart from appending "(FRAMELESS)" to the
output of "info frame", that architecture method does nothing useful
(and even this is marginal :-). I think a per frame
PRINT_EXTRA_FRAME_INFO like function would be more useful.
Alternatively, a per-frame ``frameless'' attribute could be added.
Sounds good to me!
> +const struct frame_unwind *
> +i386_frame_p (CORE_ADDR pc)
> +{
> + char *name;
> +
> + find_pc_partial_function (pc, &name, NULL, NULL);
> + if (PC_IN_SIGTRAMP (pc, name))
> + return &i386_sigtramp_frame_unwind;
The intent was for there to be one predicate function per unwinder. So
the below would be in a separate unwinder, registered separatly.
And you want me to set the right example :-). No problem.
> + return &i386_frame_unwind;
> +}
Have you tried adding just the sigtramp unwinder? I should get just
that addition debugged regardless - it should make migrating other ISAs
easier.
No I haven't. I don't think I can. The problem is that I simplified
the sigtramp unwinder a bit. However in order to do so, I need to be
able to trust the normal unwinder to unwind the stack pointer
correctly. Unfortunately the current code is a bit sloppy about this.
Mark
next prev parent reply other threads:[~2003-05-01 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 16:51 Mark Kettenis
2003-04-29 1:50 ` Andrew Cagney
2003-05-01 20:54 ` Mark Kettenis [this message]
2003-05-01 21:21 ` Andrew Cagney
2003-05-02 9:29 ` Mark Kettenis
2003-05-03 19:36 ` Andrew Cagney
2003-05-03 20:53 ` Mark Kettenis
2003-05-03 22:27 ` Daniel Jacobowitz
2003-05-04 0:28 ` 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=200305011839.h41IdPdc000324@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=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