public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] [gdb/testsuite] Add nopie in a few test-cases
Date: Thu, 13 Jul 2023 15:41:26 +0200	[thread overview]
Message-ID: <7717248b-b2e9-c44d-f7c7-a3dd102236b4@suse.de> (raw)
In-Reply-To: <88473fd2-ef80-7f7b-d283-b78bfc848a58@suse.de>

On 7/12/23 17:01, Tom de Vries wrote:
> On 7/1/23 04:55, Simon Marchi wrote:
>> On 6/17/23 06:30, Tom de Vries via Gdb-patches wrote:
>>> When running test-case gdb.arch/i386-disp-step.exp with target board
>>> unix/-m32/-fPIE/-pie we run into:
>>> ...
>>> gdb compile failed, ld: i386-disp-step0.o: warning: relocation in 
>>> read-only section `.text'
>>> ld: warning: creating DT_TEXTREL in a PIE
>>> ...
>>>
>>> Fix this by adding nopie in the compilation flags.
>>>
>>> Likewise in a few other test-cases.
>>>
>>> Tested on x86_64-linux.
>>
>> Hi Tom,
>>
>> Just to note that this causes a regression on Ubuntu 22.04.  Before:
>>
> 
> Hi Simon,
> 
> thanks for reporting this.
> 
> Is this is with a specific target board?

I've managed to reproduce this now, filed as 
https://sourceware.org/bugzilla/show_bug.cgi?id=30633 .

Thanks,
- Tom

>>      target remote localhost:2346
>>
>>      Remote debugging using localhost:2346
>>
>>      Reading symbols from /lib64/ld-linux-x86-64.so.2...
>>
>>      Reading symbols from 
>> /usr/lib/debug/.build-id/61/ef896a699bb1c2e4e231642b2e1688b2f1a61e.debug...
>>
>>      0x00007ffff7fe32b0 in _start () from /lib64/ld-linux-x86-64.so.2
>>
>>      (gdb) continue
>>
>>      Continuing.
>>
>>
>>
>>      Breakpoint 1, main () at typeddwarf.c:87
>>
>>      87    {
>>
>> After:
>>
>>      target remote localhost:2346
>>
>>      Remote debugging using localhost:2346
>>
>>      main () at typeddwarf.c:87
>>
>>      87    {
>>
>>      (gdb) continue
>>
>>      Continuing.
>>
>>
>>
>>      Program received signal SIGSEGV, Segmentation fault.
>>
>>      0x0000000000000001 in ?? ()
>>
>>      (gdb) FAIL: gdb.dwarf2/typeddwarf.exp: runto: run to main
>>
>> Simon
> 


  reply	other threads:[~2023-07-13 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17 10:30 [PATCH 1/3] [gdb/testsuite] Use require in gdb.dwarf2/implptr.exp Tom de Vries
2023-06-17 10:30 ` [PATCH 2/3] [gdb/testsuite] Add nopie in a few test-cases Tom de Vries
2023-07-01  2:55   ` Simon Marchi
2023-07-12 15:01     ` Tom de Vries
2023-07-13 13:41       ` Tom de Vries [this message]
2023-06-17 10:30 ` [PATCH 3/3] [gdb/testsuite] Remove f-string in gdb.python/py-unwind.py Tom de Vries

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=7717248b-b2e9-c44d-f7c7-a3dd102236b4@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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).