From: Mark Kettenis <kettenis@chello.nl>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
gdb-patches@sources.redhat.com, jjohnstn@redhat.com
Subject: Re: PATCH RFA: Fix MI stack frame output for synthetic frames
Date: Sun, 02 Feb 2003 17:38:00 -0000 [thread overview]
Message-ID: <861y2qtwf8.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Andrew Cagney's message of "Sun, 02 Feb 2003 00:52:24 -0500"
Andrew Cagney <ac131313@redhat.com> writes:
> > [gdb/ChangeLog]
> > 2002-11-09 Jason Molenda (jason-cl@molenda.com)
> >
> > * stack.c (print_frame_info_base): Output complete FRAME tuple
> > for synthesized frames.
> I've (finally ...) tested it and checked it in. (renamed
> inferior-mischief.c to mi-syn-frame.c though - booring).
>
> Passes fine on x86. I suspect other targets won't be so lucky.
Something must've gone wrong with your testing :-(. The stack.c
change lost us a "frame-begin" annotation when printing a DUMMY_FRAME
or a SIGTRAMP_FRAME. The latter provoked a
FAIL: gdb.base/annota1.exp: backtrace @ signal handler
on my system.
Anyway, I propose the attached fix. OK to check that in?
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* stack.c (print_frame_info): Restore call to annotate_frame_begin
lost in the previous patch.
Index: stack.c
===================================================================
RCS file: /cvs/src/src/gdb/stack.c,v
retrieving revision 1.64
diff -u -p -r1.64 stack.c
--- stack.c 2 Feb 2003 05:51:08 -0000 1.64
+++ stack.c 2 Feb 2003 17:37:44 -0000
@@ -203,6 +203,8 @@ print_frame_info (struct frame_info *fi,
struct cleanup *uiout_cleanup
= make_cleanup_ui_out_tuple_begin_end (uiout, "frame");
+ annotate_frame_begin (level == -1 ? 0 : level, get_frame_pc (fi));
+
/* Do this regardless of SOURCE because we don't have any source
to list for this frame. */
if (level >= 0)
@@ -216,7 +218,7 @@ print_frame_info (struct frame_info *fi,
ui_out_field_core_addr (uiout, "addr", fi->pc);
annotate_frame_address_end ();
}
-
+
if (get_frame_type (fi) == DUMMY_FRAME)
{
annotate_function_call ();
next prev parent reply other threads:[~2003-02-02 17:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 14:22 PATCH: " Jason Molenda
2002-11-08 14:38 ` Andrew Cagney
2002-11-08 14:46 ` Jason Molenda
2002-11-08 15:56 ` Andrew Cagney
2002-11-09 0:47 ` PATCH RFA: " Jason Molenda
2002-11-09 2:13 ` Jason Molenda
2002-11-15 11:16 ` Ping on two MI patches Jason Molenda
2003-02-02 5:52 ` PATCH RFA: Fix MI stack frame output for synthetic frames Andrew Cagney
2003-02-02 17:38 ` Mark Kettenis [this message]
2003-02-02 18:23 ` Andrew Cagney
2003-02-02 20:51 ` Mark Kettenis
2003-02-03 18:15 ` David Carlton
2003-02-03 18:27 ` Jason Molenda
2003-02-03 18:34 ` Daniel Jacobowitz
2003-02-04 8:09 ` Jason Molenda
2003-02-05 8:28 ` Jason Molenda
2003-02-05 13:59 ` Daniel Jacobowitz
2003-02-05 14:54 ` Elena Zannoni
2003-02-06 6:28 ` Fix committed for mi-syn-frames fails (was: Re: PATCH RFA: Fix MI stack frame output for synthetic frames) Jason Molenda
2003-02-06 6:31 ` Jason Molenda
2003-02-06 17:01 ` David Carlton
2003-02-06 18:21 ` Andrew Cagney
2003-02-06 18:27 ` Jason Molenda
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=861y2qtwf8.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jason-swarelist@molenda.com \
--cc=jjohnstn@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