From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] [gdb/testsuite] Drop -nostdlib in gdb.dwarf2/typeddwarf.exp
Date: Wed, 26 Jul 2023 13:47:45 +0200 [thread overview]
Message-ID: <001f58cd-3479-0a51-7148-974d531bfc27@suse.de> (raw)
In-Reply-To: <da6fae9a-1bd9-e0dd-f12d-8f9d986fdc00@simark.ca>
On 7/24/23 18:21, Simon Marchi wrote:
> On 7/13/23 10:15, Tom de Vries via Gdb-patches wrote:
>> As reported in PR testsuite/30633, when running test-case
>> gdb.dwarf2/typeddwarf.exp with target board native-gdbserver on Ubuntu
>> 22.04.2, we run into:
>> ...
>> (gdb) continue^M
>> Continuing.^M
>> ^M
>> Program received signal SIGSEGV, Segmentation fault.^M
>> 0x0000000000000001 in ?? ()^M
>> (gdb) FAIL: gdb.dwarf2/typeddwarf.exp: runto: run to main
>> ...
>>
>> We run into the FAIL as follows:
>> - due to using gdbserver, we attach at the point of the first instruction, in
>> _start
>> - we then set a breakpoint at main
>> - the test-case is a .s file, that has main renamed to _start in the assembly,
>> but not in the debuginfo
>> - setting a breakpoint at main sets the breakpoint at the same instruction
>> we're currently stopped at
>> - continue doesn't hit the breakpoint, and we return out of _start, which
>> causes a sigsegv
>>
>> Note that this is for the amd64 case (using gdb.dwarf2/typeddwarf-amd64.S).
>> For the i386 case (using gdb.dwarf2/typeddwarf.S), setting a breakpoint in
>> main sets it one insn after function entry, and consequently the problem does
>> not occur.
>>
>> The FAIL is a regression since commit 90cce6c0551 ("[gdb/testsuite] Add nopie
>> in a few test-cases").
>>
>> Without nopie the executable is PIE, with nopie it's static instead.
>>
>> In the PIE case, we attach at the point of _start in the dynamic linker, and
>> consequently we do not skip the breakpoint in main, and also don't run into
>> the FAIL.
>>
>> Fix this by:
>> - removing the -nostdlib setting, and
>> - renaming _start to main in both .S files.
>>
>> The change to use -nostdlib and rename main to _start was originally added
>> in commit 6edba76fe8b (submitted here:
>> https://sourceware.org/pipermail/gdb-patches/2011-May/082657.html ) , I assume
>> to fix the problem now fixed by using nopie.
>>
>> Tested on x86_64-linux.
>>
>> Reported-By: Simon Marchi <simon.marchi@efficios.com>
>> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30633
>
> I have not dug in the code at all, but I confirm that the patch fixes
> the test. Therefore:
>
> Tested-By: Simon Marchi <simon.marchi@efficios.com>
Thanks for testing, committed.
- Tom
prev parent reply other threads:[~2023-07-26 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 14:15 Tom de Vries
2023-07-24 16:21 ` Simon Marchi
2023-07-26 11:47 ` 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=001f58cd-3479-0a51-7148-974d531bfc27@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).