public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27743] Internal error psymtab.c
Date: Mon, 19 Apr 2021 14:45:59 +0000 [thread overview]
Message-ID: <bug-27743-4717-qTkyvJT4Yb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27743-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27743
--- Comment #15 from Simon Marchi <simark at simark dot ca> ---
(In reply to Ethan Zhang from comment #11)
> I have found it to be related to link time optimization and setting a break
> point with absolute path.
>
> Compile a piece of source code with gcc9 using link time optimization, for
> example:
> g++-9 -ggdb -flto test.cpp -o test
>
> Load "test" into GDB 10, then set break point using absolute path:
> break /path/to/test:(line number)
>
> That should be enough to reproduce the issue.
>
> And it seems to only appear when the program is compiled with gcc9 with lto,
> debug using gdb10 and have a break point set in absolute path.
>
> The content of the source code doesn't seem to make a difference.
> If the source code is compiled in gcc10 with lto, this issue doesn't appear.
> If the break point is set through relative path, this issue doesn't appear.
Oh, that triggers the bug for me indeed! Here's my full setup:
- Ubuntu 20.04
- Package gcc-arm-none-eabi (arm-none-eabi-gcc (15:9-2019-q4-0ubuntu1) 9.2.1
20191025 (release) [ARM/arm-9-branch revision 277599])
- Source file:
---8<---
extern "C" void _exit(int code)
{
for (;;);
}
int main(void) {
return 0;
}
--->8---
- Compiler command: arm-none-eabi-g++ -ggdb -flto test.cpp -o test
- GDB command:
$ ./gdb -nx -q --data-directory=data-directory ~/test -ex "b
/home/smarchi/test.cpp:7"
Reading symbols from /home/smarchi/test...
/home/smarchi/src/binutils-gdb/gdb/psymtab.c:132: internal-error: bool
partial_map_expand_apply(objfile*, const char*, const char*, partial_symtab*,
gdb::function_view<bool(symtab*)>): Assertion `pst->user == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
I'll attach the binary shortly.
And indeed, I don't see the problem with master.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-19 14:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 12:57 [Bug gdb/27743] New: " ilia.motornyi at jetbrains dot com
2021-04-16 13:12 ` [Bug gdb/27743] " ilia.motornyi at jetbrains dot com
2021-04-16 14:09 ` simark at simark dot ca
2021-04-16 14:31 ` ilia.motornyi at jetbrains dot com
2021-04-17 3:04 ` cn.yiki at gmail dot com
2021-04-17 13:06 ` simark at simark dot ca
2021-04-17 15:46 ` tromey at sourceware dot org
2021-04-18 4:56 ` cn.yiki at gmail dot com
2021-04-19 0:56 ` simark at simark dot ca
2021-04-19 0:56 ` simark at simark dot ca
2021-04-19 1:51 ` tromey at sourceware dot org
2021-04-19 1:54 ` simark at simark dot ca
2021-04-19 11:55 ` cn.yiki at gmail dot com
2021-04-19 14:04 ` ilia.motornyi at jetbrains dot com
2021-04-19 14:23 ` cn.yiki at gmail dot com
2021-04-19 14:41 ` ilia.motornyi at jetbrains dot com
2021-04-19 14:45 ` simark at simark dot ca [this message]
2021-04-19 14:46 ` simark at simark dot ca
2021-04-23 12:03 ` ilia.motornyi at jetbrains dot com
2021-04-23 12:54 ` ilia.motornyi at jetbrains dot com
2021-04-23 15:27 ` tromey at sourceware dot org
2021-04-23 15:34 ` tromey at sourceware dot org
2021-04-23 18:14 ` tromey at sourceware dot org
2021-04-23 18:23 ` tromey at sourceware dot org
2021-04-23 18:49 ` brobecker at gnat dot com
2021-04-26 15:39 ` cvs-commit at gcc dot gnu.org
2021-04-26 15:40 ` cvs-commit at gcc dot gnu.org
2021-04-26 15:53 ` cvs-commit at gcc dot gnu.org
2021-04-26 15:55 ` tromey at sourceware dot org
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=bug-27743-4717-qTkyvJT4Yb@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).