Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/dwarf: fix reading subprogram with DW_AT_specification (PR gdb/26693)
Date: Tue, 20 Oct 2020 12:48:02 -0400	[thread overview]
Message-ID: <ac13c72e-1d0a-9e8f-a4b2-2df6128552a1@polymtl.ca> (raw)
In-Reply-To: <ceb8898a-694d-ceea-0da0-4287141e07b8@suse.de>

On 2020-10-20 12:29 p.m., Tom de Vries wrote:
> Consider using:
> ...
> standard_testfile main.c .S
> ...
> and dropping gdb.dwarf2/template-specification-full-name.c.

Done.

> I applied the patch on trunk and ran the tests, and ran into:
> ...
> (gdb) print apply<int>^M
> Cannot access memory at address 0x1234^M
> (gdb) FAIL: gdb.dwarf2/template-specification-full-name.exp: print
> apply<int>
> ...
>
> So I guess we'll have to fix the hardcoded high/low.

Ok, I can reproduce if I produce a non-PIE (with the nopie compile
option).

> Using this instead works for me, in combination with using main.c
> (otherwise the main_label is missing):
> ...
>                 {MACRO_AT_range {main}}
> ...

Thanks, I'll use that.

Simon

  reply	other threads:[~2020-10-20 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 14:18 Simon Marchi via Gdb-patches
2020-10-20 15:13 ` Simon Marchi via Gdb-patches
2020-10-20 15:55   ` Strasuns, Mihails via Gdb-patches
2020-10-20 16:29   ` Tom de Vries
2020-10-20 16:48     ` Simon Marchi via Gdb-patches [this message]
2020-10-20 16:50       ` [PATCH v2] " Simon Marchi via Gdb-patches
2020-10-21 20:42         ` Tom Tromey
2020-10-22  2:37           ` Simon Marchi via Gdb-patches
2020-10-22 14:18             ` Tom Tromey
2020-10-22 14:51               ` Simon Marchi via Gdb-patches

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=ac13c72e-1d0a-9e8f-a4b2-2df6128552a1@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    /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