From: Pedro Alves <palves@redhat.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type
Date: Wed, 10 Feb 2016 15:34:00 -0000 [thread overview]
Message-ID: <56BB5872.2000604@redhat.com> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B233326016F@IRSMSX104.ger.corp.intel.com>
On 02/10/2016 03:02 PM, Metzger, Markus T wrote:
> No new fails there, as well (64-bit IA).
>
> I added a comment based on your statement that frame_unwind_caller_xxx
> callers should check frame_unwind_caller_id and assert that skip_artificial_frames
> does not return NULL.
>
> Info frame doesn't crash.
>
> (gdb) info frame
> Stack level 0, frame at 0x0:
> rip = 0x4005b0 in bar (tailcall-only.c:29); saved rip = 0x4005c2
> called by frame at 0x0
^^^^^^^^^^^^^^^
> source language c.
> Arglist at unknown address.
> Locals at unknown address,Registers are not available in btrace record history
>
> This is from a tailcall-only frame stack in replay mode using the tailcall-only test.
> The real caller has not been recorded.
Not sure how you got that, since "called by frame" seems to indicates that
the frame was not TAILCALL_FRAME:
else if (get_frame_type (fi) == TAILCALL_FRAME)
puts_filtered (" tail call frame");
else if (get_frame_type (fi) == INLINE_FRAME)
printf_filtered (" inlined into frame %d",
frame_relative_level (get_prev_frame (fi)));
else
{
printf_filtered (" called by frame at ");
fputs_filtered (paddress (gdbarch, get_frame_base (calling_frame_info)),
gdb_stdout);
}
>
> The output isn't very helpful for record btrace since we don't record register and
> memory changes.
So I'm mostly OK with the patch now, but I think you should dig a bit more
into the "info frame" output, since I think you _will_ internal error with a
TAILCALL_FRAME.
My remaining issue is now with the user-visible strings.
> @@ -985,6 +1007,10 @@ frame_pop (struct frame_info *this_frame)
> entering THISFRAME. */
> prev_frame = skip_tailcall_frames (prev_frame);
>
> + /* We cannot pop tailcall frames. */
> + if (prev_frame == NULL)
> + error (_("Cannot pop a tailcall frame."));
> +
I find this confusing, from a user perspective. AFAIK, you can pop a tailcall
frame; what you can't do is pop when you don't know anything about the frame
that started the tail calling. How about:
if (prev_frame == NULL)
error (_("Cannot return: tailcall caller frame not found."));
s/pop/return/, as "pop" is an internal implementation detail.
(I suggest also dropping the redundant comment.)
> + {
> + /* Ignore TAILCALL_FRAME type frames, they were executed already before
> + entering THISFRAME. */
> + frame = skip_tailcall_frames (frame);
> +
> + if (frame == NULL)
> + error (_("\"finish\" not meaningful for tailcall frames."));
> +
if (frame == NULL)
error (_("Cannot finish: tailcall caller frame not found."));
(I'd also be fine with dropping the "Cannot xxx:" part to make
the error messages the same in both cases.)
> + finish_forward (sm, frame);
> + }
> }
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-02-10 15:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 14:18 [PATCH v2 1/3] frame: add skip_tailcall_frames Markus Metzger
2016-02-05 14:18 ` [PATCH v2 2/3] frame: use get_prev_frame_always in skip_tailcall_frames Markus Metzger
2016-02-07 13:01 ` Joel Brobecker
2016-02-08 8:14 ` Metzger, Markus T
2016-02-09 11:42 ` Pedro Alves
2016-02-09 11:58 ` Joel Brobecker
2016-02-09 14:25 ` Metzger, Markus T
2016-02-09 14:41 ` Pedro Alves
[not found] ` <A78C989F6D9628469189715575E55B233325FCA0@IRSMSX104.ger.corp.intel.com>
2016-02-15 9:51 ` Metzger, Markus T
2016-02-17 15:32 ` Pedro Alves
2016-02-19 11:36 ` Metzger, Markus T
2016-02-09 14:44 ` Joel Brobecker
2016-02-05 14:19 ` [PATCH v2 3/3] btrace, frame: fix crash in get_frame_type Markus Metzger
2016-02-09 12:05 ` Pedro Alves
2016-02-09 14:43 ` Metzger, Markus T
2016-02-09 22:01 ` Pedro Alves
2016-02-10 7:40 ` Metzger, Markus T
2016-02-10 9:59 ` Pedro Alves
2016-02-10 10:29 ` Metzger, Markus T
2016-02-10 15:02 ` Metzger, Markus T
2016-02-10 15:34 ` Pedro Alves [this message]
2016-02-11 9:51 ` Metzger, Markus T
2016-02-11 13:39 ` Pedro Alves
2016-02-11 15:42 ` Metzger, Markus T
2016-02-11 15:58 ` Pedro Alves
2016-02-11 16:07 ` Metzger, Markus T
2016-02-07 13:00 ` [PATCH v2 1/3] frame: add skip_tailcall_frames Joel Brobecker
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=56BB5872.2000604@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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