public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/30648] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
@ 2023-07-18 7:45 vries at gcc dot gnu.org
2023-07-18 11:00 ` [Bug gdb/30648] " vries at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 7:45 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30648
Bug ID: 30648
Summary: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit
breakpoint in outer gdb again
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With a gdb build with -O2 -flto, I run into:
...
(gdb) PASS: gdb.gdb/python-helper.exp: resume inner gdb again
ptype global_c^M
^M
Thread 1 "xgdb" hit Breakpoint 3,
_Z12c_print_typeP4typePKcP7ui_fileii8languagePK18type_print_options () at
/data/vries/gdb/src/gdb/c-typeprint.c:175^M
175 {^M
(outer-gdb) FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug gdb/30648] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
2023-07-18 7:45 [Bug gdb/30648] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again vries at gcc dot gnu.org
@ 2023-07-18 11:00 ` vries at gcc dot gnu.org
2023-07-18 12:32 ` vries at gcc dot gnu.org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 11:00 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30648
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
This is with gcc 7.5.0 on openSUSE Leap 15.4.
With gcc 13.1.1 on openSUSE Tumbleweed, this doesn't occur.
AFAICT, gdb is not wrong. The CU containing the declaration for c_print_type
has language "non-ANSI C" rather than C++, and this explains why the function
name is not demangled.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug gdb/30648] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
2023-07-18 7:45 [Bug gdb/30648] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again vries at gcc dot gnu.org
2023-07-18 11:00 ` [Bug gdb/30648] " vries at gcc dot gnu.org
@ 2023-07-18 12:32 ` vries at gcc dot gnu.org
2023-07-18 12:32 ` [Bug testsuite/30648] " vries at gcc dot gnu.org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 12:32 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30648
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> This is with gcc 7.5.0 on openSUSE Leap 15.4.
>
> With gcc 13.1.1 on openSUSE Tumbleweed, this doesn't occur.
Also not reproducible with gcc 8.2.1.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug testsuite/30648] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
2023-07-18 7:45 [Bug gdb/30648] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again vries at gcc dot gnu.org
2023-07-18 11:00 ` [Bug gdb/30648] " vries at gcc dot gnu.org
2023-07-18 12:32 ` vries at gcc dot gnu.org
@ 2023-07-18 12:32 ` vries at gcc dot gnu.org
2023-07-19 7:18 ` cvs-commit at gcc dot gnu.org
2023-07-19 7:19 ` vries at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 12:32 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30648
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|gdb |testsuite
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug testsuite/30648] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
2023-07-18 7:45 [Bug gdb/30648] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again vries at gcc dot gnu.org
` (2 preceding siblings ...)
2023-07-18 12:32 ` [Bug testsuite/30648] " vries at gcc dot gnu.org
@ 2023-07-19 7:18 ` cvs-commit at gcc dot gnu.org
2023-07-19 7:19 ` vries at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-07-19 7:18 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30648
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0d332f11122473192a944230e1d925bac115ca0d
commit 0d332f11122473192a944230e1d925bac115ca0d
Author: Tom de Vries <tdevries@suse.de>
Date: Wed Jul 19 09:18:29 2023 +0200
[gdb/testsuite] Fix gdb.gdb/python-helper.exp with -O2 -flto=auto and gcc
7.5.0
With a gdb build with -O2 -flto=auto using gcc 7.5.0, I run into:
...
(gdb) ptype global_c^M
^M
Thread 1 "xgdb" hit Breakpoint 3, \
_Z12c_print_typeP4typePKcP7ui_fileii8languagePK18type_print_options () at
\
gdb/c-typeprint.c:175^M
175 {^M
(outer-gdb) FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb
again
...
This is a problem with the debug info, which marks the CU containing the
function declaration as C rather than C++. This is fixed in gcc 8 and
later.
Work around this compiler problem by allowing the mangled name.
Tested on x86_64-linux.
PR testsuite/30648
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30648
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug testsuite/30648] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again
2023-07-18 7:45 [Bug gdb/30648] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again vries at gcc dot gnu.org
` (3 preceding siblings ...)
2023-07-19 7:18 ` cvs-commit at gcc dot gnu.org
@ 2023-07-19 7:19 ` vries at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 7:19 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30648
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |14.1
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-07-19 7:19 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-18 7:45 [Bug gdb/30648] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: hit breakpoint in outer gdb again vries at gcc dot gnu.org
2023-07-18 11:00 ` [Bug gdb/30648] " vries at gcc dot gnu.org
2023-07-18 12:32 ` vries at gcc dot gnu.org
2023-07-18 12:32 ` [Bug testsuite/30648] " vries at gcc dot gnu.org
2023-07-19 7:18 ` cvs-commit at gcc dot gnu.org
2023-07-19 7:19 ` vries at gcc dot gnu.org
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).