From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb.dwarf2: Define and use gdb_target_symbol_prefix for symbol prefixes
Date: Thu, 05 Nov 2015 22:26:00 -0000 [thread overview]
Message-ID: <20151105152616.18e00a5c@pinnacle.lan> (raw)
In-Reply-To: <563BC7C9.3040404@redhat.com>
On Thu, 05 Nov 2015 21:19:05 +0000
Pedro Alves <palves@redhat.com> wrote:
> On 11/05/2015 08:01 PM, Kevin Buettner wrote:
> > On Thu, 05 Nov 2015 10:14:09 +0000
> > Pedro Alves <palves@redhat.com> wrote:
>
> >> > Not sure I see what makes gdb.dwarf2/atomic-type.exp different?
> >> > E.g., the gdb.dwarf2/dw2-bad-mips-linkage-name.exp hunk looks quite
> >> > similar. What makes gdb.dwarf2/atomic-type.exp special?
> > I was mistaken. Both of these tests - dw2-bad-mips-linkage-name.exp
> > and atomic-type.exp - have problems due to the fact that the call to
> > gdb_target_symbol appears within a DW_TAG_ construct. The proc
> > _handle_DW_TAG performs command and variable expansion within a DW_TAG_
> > construct. (It does other things too.)
>
> ...
>
> > --- a/gdb/testsuite/gdb.dwarf2/dw2-regno-invalid.exp
> > +++ b/gdb/testsuite/gdb.dwarf2/dw2-regno-invalid.exp
> ...
> > compile_unit {
> > - {low_pc main DW_FORM_addr}
> > - {high_pc main+0x10000 DW_FORM_addr}
> > + {low_pc [gdb_target_symbol main] DW_FORM_addr}
> > + {high_pc [gdb_target_symbol main]+0x10000 DW_FORM_addr}
> > } {
> > declare_labels integer_label
> >
> > @@ -43,8 +43,8 @@ Dwarf::assemble $asm_file {
> > DW_TAG_subprogram {
> > {name main}
> > {DW_AT_external 1 flag}
> > - {low_pc main DW_FORM_addr}
> > - {high_pc main+0x10000 DW_FORM_addr}
> > + {low_pc [gdb_target_symbol main] DW_FORM_addr}
> > + {high_pc [gdb_target_symbol main]+0x10000 DW_FORM_addr}
>
> Aren't these above more instances that needed the "join"? I believe
> so, but if not, I'd like to understand why not.
You're right; they did.
> The patch looks good to me otherwise.
Thanks again for your review.
I've pushed it.
Kevin
prev parent reply other threads:[~2015-11-05 22:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 11:06 Kevin Buettner
2015-10-30 12:06 ` Kevin Buettner
2015-10-30 15:53 ` Pedro Alves
2015-11-05 6:39 ` Kevin Buettner
2015-11-05 10:46 ` Pedro Alves
2015-11-05 10:55 ` Pedro Alves
2015-11-06 5:33 ` Kevin Buettner
2015-10-30 15:51 ` Pedro Alves
2015-11-04 21:49 ` Kevin Buettner
2015-11-05 10:14 ` Pedro Alves
2015-11-05 20:01 ` Kevin Buettner
2015-11-05 21:19 ` Pedro Alves
2015-11-05 22:26 ` Kevin Buettner [this message]
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=20151105152616.18e00a5c@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
/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