From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Fix "info frame" in the outermost frame.
Date: Mon, 02 Dec 2013 10:05:00 -0000 [thread overview]
Message-ID: <529C5B70.9040308@redhat.com> (raw)
In-Reply-To: <529C4CB4.2070002@codesourcery.com>
On 12/02/2013 09:02 AM, Yao Qi wrote:
> On 11/30/2013 04:15 AM, Pedro Alves wrote:
>> A new test is added. It's based off dw2-reg-undefined.exp, and tweaked to
>> mark the return address (rip) of "stop_frame" as undefined.
>
> Can we use dwarf assembler to create needed dwarf info?
Yeah, I had the same question for the dwarf2-unspecified-ret-addr.exp
test (that has been reverted meanwhile), but the dwarf assembler
doesn't do CFI.
--
Pedro Alves
next prev parent reply other threads:[~2013-12-02 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:16 [PATCH 0/2] " Pedro Alves
2013-11-29 20:20 ` [PATCH 2/2] " Pedro Alves
2013-12-02 9:04 ` Yao Qi
2013-12-02 10:05 ` Pedro Alves [this message]
[not found] ` <52A3DBA6.6060706@codesourcery.com>
2013-12-09 10:58 ` Pedro Alves
2013-11-29 20:39 ` [PATCH 1/2] New OPTIMIZED_OUT_ERROR error code Pedro Alves
2013-12-02 13:53 ` Andrew Burgess
2013-12-06 20:01 ` [PATCH 0/2] Fix "info frame" in the outermost frame 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=529C5B70.9040308@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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