From: Enze Li <enze.li@hotmail.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org, enze.li@gmx.com
Subject: Re: [PATCH] gdb/testsuite: fix an issue that prevents selftest
Date: Wed, 07 Dec 2022 21:37:54 +0800 [thread overview]
Message-ID: <OS3P286MB2152E0F680BE1378192FD576F01A9@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <9c42e79b-e04b-5c58-2a00-0c93c4358ce6@simark.ca> (Simon Marchi's message of "Mon, 5 Dec 2022 14:50:24 -0500")
On Mon, Dec 05 2022 at 02:50:24 PM -0500, Simon Marchi wrote:
> On 12/4/22 09:18, Enze Li via Gdb-patches wrote:
>> When running gdb.gdb/selftest.exp, I see the following warning,
>> ...
>> (gdb) break captured_main
>> Breakpoint 1 at 0x4fdab2
>> (gdb) run -nw -nx -iex "set height 0" -iex "set width 0"
>> Starting program:
>> /home/lee/dev/binutils-gdb/gdb/testsuite/outputs/gdb.gdb/selftest/xgdb
>> -nw -nx -iex "set height 0" -iex "set width 0"
>> [Thread debugging using libthread_db enabled]
>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>
>> Breakpoint 1, 0x0000555555a51ab2 in captured_main(void*) ()
>> (gdb) FAIL: gdb.gdb/selftest.exp: run until breakpoint at captured_main
Hi Simon,
Thanks for your review.
>
> Doesn't this look like a bug to you? What is the extra `()` at the end
> of the line?
Hmmm...After digging into it further, I realized that this patch doesn't
fix the root cause; please drop this patch.
Before running the testcase, I used CXXFLAGS="-std=gnu++11" to compile
GDB, which overrides the default "-O2 -g", and directly causes the
compiled GDB to have no debug information. I think this may have caused
the problem. Is that what it is?
The extra `()` is supposed to show the arguments, but since it does not
have debugging information, it is empty here.
I sent a new patch to the list to fix the root cause, you might want to
have a look. :)
Best Regards,
Enze
prev parent reply other threads:[~2022-12-07 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 14:18 Enze Li
2022-12-05 19:50 ` Simon Marchi
2022-12-07 13:37 ` Enze Li [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=OS3P286MB2152E0F680BE1378192FD576F01A9@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM \
--to=enze.li@hotmail.com \
--cc=enze.li@gmx.com \
--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).