Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Kevin Buettner <kevinb@redhat.com>,
	gdb-patches@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH][gdb] Fix gdb.dwarf2/varval.exp with -fPIE/-pie
Date: Fri, 09 Aug 2019 04:50:00 -0000	[thread overview]
Message-ID: <68956239-d105-8df0-dcb4-081d308b1122@suse.de> (raw)
In-Reply-To: <20190808110418.378470a7@f29-4.lan>

[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

On 08-08-19 20:04, Kevin Buettner wrote:
> On Thu, 08 Aug 2019 11:16:44 -0600
> Tom Tromey <tom@tromey.com> wrote:
> 
>>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:  
>>
>> Thanks for the patch.
>>
>> Tom> +      CORE_ADDR baseaddr
>> Tom> +	= ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT (objfile));
>> Tom> +      struct gdbarch *gdbarch = get_objfile_arch (objfile);  
>>  
>> Tom>        for (const auto &cand_off
>> Tom>  	     : dwarf2_per_objfile->abstract_to_concrete[die->sect_off])
>> Tom> @@ -23220,6 +23223,8 @@ dwarf2_fetch_die_loc_sect_off (sect_offset sect_off,  
>>  
>> Tom>  	  CORE_ADDR pc_low, pc_high;
>> Tom>  	  get_scope_pc_bounds (cand->parent, &pc_low, &pc_high, cu);
>> Tom> +	  pc_low = gdbarch_adjust_dwarf2_addr (gdbarch, pc_low + baseaddr);
>> Tom> +	  pc_high = gdbarch_adjust_dwarf2_addr (gdbarch, pc_high + baseaddr);
>> Tom>  	  if (pc_low == ((CORE_ADDR) -1)  
>>
>> I think this test has to precede the offsetting.

Ouch, thanks for catching that.

> 
> Yes, I agree.
> 
> It appears to me that the test / continue in its entirety...
> 
> 	  if (pc_low == ((CORE_ADDR) -1)
> 	      || !(pc_low <= pc && pc < pc_high))
> 	    continue;
> 
> ...will need to be split with the -1 part being performed before the
> pc_low/pc_high adjustment and the other part being performed after.

Done.

Committed as attached.

Thanks,
- Tom



[-- Attachment #2: 0001-gdb-Fix-gdb.dwarf2-varval.exp-with-fPIE-pie.patch --]
[-- Type: text/x-patch, Size: 1839 bytes --]

[gdb] Fix gdb.dwarf2/varval.exp with -fPIE/-pie

With target board unix/-fPIE/-pie, we get:
...
FAIL: gdb.dwarf2/varval.exp: print varval2
...

This is due comparing a get_frame_pc result (which includes the for PIE
non-zero relocation offset) with pc_high and pc_low obtained using
get_scope_pc_bounds (which do not include the relocation offset).

Fix this by adjusting pc_high and pc_low with the relocation offset.

Tested on x86_64-linux with target board unix/-fPIE/-pie.

gdb/ChangeLog:

2019-08-08  Tom de Vries  <tdevries@suse.de>

	PR gdb/24591
	* dwarf2read.c (dwarf2_fetch_die_loc_sect_off): Adjust pc_high and
	pc_low with relocation offset.

---
 gdb/dwarf2read.c | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index 1c26f8355f..de9755f6ce 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -23206,6 +23206,9 @@ dwarf2_fetch_die_loc_sect_off (sect_offset sect_off,
 	  != dwarf2_per_objfile->abstract_to_concrete.end ()))
     {
       CORE_ADDR pc = (*get_frame_pc) (baton);
+      CORE_ADDR baseaddr
+	= ANOFFSET (objfile->section_offsets, SECT_OFF_TEXT (objfile));
+      struct gdbarch *gdbarch = get_objfile_arch (objfile);
 
       for (const auto &cand_off
 	     : dwarf2_per_objfile->abstract_to_concrete[die->sect_off])
@@ -23220,8 +23223,11 @@ dwarf2_fetch_die_loc_sect_off (sect_offset sect_off,
 
 	  CORE_ADDR pc_low, pc_high;
 	  get_scope_pc_bounds (cand->parent, &pc_low, &pc_high, cu);
-	  if (pc_low == ((CORE_ADDR) -1)
-	      || !(pc_low <= pc && pc < pc_high))
+	  if (pc_low == ((CORE_ADDR) -1))
+	    continue;
+	  pc_low = gdbarch_adjust_dwarf2_addr (gdbarch, pc_low + baseaddr);
+	  pc_high = gdbarch_adjust_dwarf2_addr (gdbarch, pc_high + baseaddr);
+	  if (!(pc_low <= pc && pc < pc_high))
 	    continue;
 
 	  die = cand;

      reply	other threads:[~2019-08-09  4:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08 12:49 Tom de Vries
2019-08-08 17:16 ` Tom Tromey
2019-08-08 18:04   ` Kevin Buettner
2019-08-09  4:50     ` Tom de Vries [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=68956239-d105-8df0-dcb4-081d308b1122@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=tom@tromey.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