From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 3/3] btrace, frame: fix crash in get_frame_type
Date: Thu, 11 Feb 2016 16:26:00 -0000 [thread overview]
Message-ID: <56BCB630.50302@redhat.com> (raw)
In-Reply-To: <1455207283-12660-3-git-send-email-markus.t.metzger@intel.com>
On 02/11/2016 04:14 PM, Markus Metzger wrote:
> 2016-02-11 Markus Metzger <markus.t.metzger@intel.com>
>
> gdb/
> * frame.h (skip_tailcall_frames): Update comment.
> * frame.c (skip_artificial_frames, skip_tailcall_frames): Return NULL
> if only artificial frames are found. Update comment.
> (frame_unwind_caller_id): Handle NULL return.
> (frame_unwind_caller_pc, frame_unwind_caller_arch): Assert that
> skip_artificial_frames does not return NULL.
> (frame_pop): Add an error if only tailcall frames are found.
> * infcmd.c (finish_command): Move skip_tailcall_frames call into forward-
> execution case. Add an error if only tailcall frames are found.
>
> testsuite/
> * gdb.btrace/tailcall-only.exp: New.
> * gdb.btrace/tailcall-only.c: New.
> * gdb.btrace/x86_64-tailcall-only.S: New.
> * gdb.btrace/i686-tailcall-only.S: New.
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-02-11 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 16:14 [PATCH v3 1/3] frame: add skip_tailcall_frames Markus Metzger
2016-02-11 16:15 ` [PATCH v3 3/3] btrace, frame: fix crash in get_frame_type Markus Metzger
2016-02-11 16:26 ` Pedro Alves [this message]
2016-02-11 16:15 ` [PATCH v3 2/3] stack: check frame_unwind_caller_id Markus Metzger
2016-02-11 16:21 ` Pedro Alves
2016-07-21 16:35 ` Yao Qi
2016-07-22 7:53 ` Metzger, Markus T
2016-02-11 16:21 ` [PATCH v3 1/3] frame: add skip_tailcall_frames Pedro Alves
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=56BCB630.50302@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