From: Yao Qi <yao@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb@sourceware.org>
Subject: Re: Symbol can't be found unless type 'tab'
Date: Wed, 12 Sep 2012 13:37:00 -0000 [thread overview]
Message-ID: <50508FEC.5030701@codesourcery.com> (raw)
In-Reply-To: <20120912123247.GA23476@host2.jankratochvil.net>
On 09/12/2012 08:32 PM, Jan Kratochvil wrote:
> On Wed, 12 Sep 2012 13:33:34 +0200, Yao Qi wrote:
>> On 09/12/2012 04:06 PM, Jan Kratochvil wrote:
>>> Why didn't use just normal DWARF block, instead of the location list?
>>> This part does not matter for your testcase and it will work with GDB.
>>
>> No special reason really. Are you suggesting create dwarf like this?
>>
>> <1><33>: Abbrev Number: 3 (DW_TAG_variable)
>> <34> DW_AT_name : i
>> <36> DW_AT_type : <0x2a>
>> <3a> DW_AT_external : 1
>> <3b> DW_AT_location : 6 byte block: 52 93 4 53 93 4
>> (DW_OP_reg2 (edx); DW_OP_piece: 4; DW_OP_reg3 (ebx); DW_OP_piece: 4)
>
> Oops, you are right, this also cannot work.
>
I am not sure what do you mean by "this also cannot work", but it works
for me, at least for my test purpose.
(gdb) b middle_middle
Breakpoint 1 at 0x80483ca
(gdb) run
Starting program:
/home/yao/Source/gnu/gdb/build-git/x86/gdb/testsuite/gdb.mi/mi-reg-changed
Breakpoint 1, 0x080483ca in middle_middle ()
(gdb) p/x i
$2 = 0x45396ff4bfffefe4
(gdb) p/x $ebx
$3 = 0x45396ff4
(gdb) p/x $edx
$4 = 0xbfffefe4
--
Yao
next prev parent reply other threads:[~2012-09-12 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 12:52 Yao Qi
2012-09-10 13:18 ` Jan Kratochvil
2012-09-12 7:45 ` Yao Qi
2012-09-12 8:07 ` Jan Kratochvil
2012-09-12 11:34 ` Yao Qi
2012-09-12 12:33 ` Jan Kratochvil
2012-09-12 13:37 ` Yao Qi [this message]
2012-09-12 13:45 ` Jan Kratochvil
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=50508FEC.5030701@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).