public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
@ 2023-07-18 11:49 vries at gcc dot gnu.org
2023-07-18 14:11 ` [Bug symtab/30650] " vries at gcc dot gnu.org
` (12 more replies)
0 siblings, 13 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 11:49 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
Bug ID: 30650
Summary: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print
all_bfds
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: testsuite
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With a gdb build with -O2 -flto=auto using gcc 9.3.1, I get:
...
(outer-gdb) PASS: gdb.gdb/python-helper.exp: print *type->main_type
print all_bfds^M
$7 = <optimized out>^M
(outer-gdb) FAIL: gdb.gdb/python-helper.exp: print all_bfds
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
@ 2023-07-18 14:11 ` vries at gcc dot gnu.org
2023-07-18 15:21 ` vries at gcc dot gnu.org
` (11 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 14:11 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|testsuite |symtab
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Hmm, doesn't happen with -readnow, this seems to be a symtab issue.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
2023-07-18 14:11 ` [Bug symtab/30650] " vries at gcc dot gnu.org
@ 2023-07-18 15:21 ` vries at gcc dot gnu.org
2023-07-18 17:09 ` vries at gcc dot gnu.org
` (10 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 15:21 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
It doesn't reproduce 100%:
...
$ gdb -q -batch ./gdb-x -ex "print all_bfds"
$1 = (htab_t) 0x0
$ gdb -q -batch ./gdb-x -ex "print all_bfds"
$1 = <optimized out>
$ gdb -q -batch ./gdb-x -ex "print all_bfds"
$1 = <optimized out>
$ gdb -q -batch ./gdb-x -ex "print all_bfds"
$1 = <optimized out>
$ gdb -q -batch ./gdb-x -ex "print all_bfds"
$1 = <optimized out>
$ gdb -q -batch ./gdb-x -ex "print all_bfds"
$1 = (htab_t) 0x0
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
2023-07-18 14:11 ` [Bug symtab/30650] " vries at gcc dot gnu.org
2023-07-18 15:21 ` vries at gcc dot gnu.org
@ 2023-07-18 17:09 ` vries at gcc dot gnu.org
2023-07-19 7:06 ` vries at gcc dot gnu.org
` (9 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-18 17:09 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Reproduces with gdb-13-branch, doesn't reproduce with gdb-12-branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (2 preceding siblings ...)
2023-07-18 17:09 ` vries at gcc dot gnu.org
@ 2023-07-19 7:06 ` vries at gcc dot gnu.org
2023-07-19 7:16 ` vries at gcc dot gnu.org
` (8 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 7:06 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> It doesn't reproduce 100%:
Reproduces 100% with "maint set worker-threads 0":
...
$ for n in $(seq 1 10); do \
gdb -q -batch -eiex "maint set worker-threads 0" ./gdb-x \
-ex "print all_bfds"; \
done
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (3 preceding siblings ...)
2023-07-19 7:06 ` vries at gcc dot gnu.org
@ 2023-07-19 7:16 ` vries at gcc dot gnu.org
2023-07-19 9:03 ` vries at gcc dot gnu.org
` (7 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 7:16 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
In terms of debug info, we're dealing with a forward inter-CU reference to an
abstract origin:
...
<0><14b64e8>: Abbrev Number: 1 (DW_TAG_compile_unit)
...
<1><14fc06f>: Abbrev Number: 45 (DW_TAG_variable)
<14fc070> DW_AT_abstract_origin: <0x5355817>
<14fc074> DW_AT_location : (DW_OP_addr: 1fd8be8)
...
<0><530411b>: Abbrev Number: 235 (DW_TAG_compile_unit)
...
<1><5355817>: Abbrev Number: 95 (DW_TAG_variable)
<5355818> DW_AT_name : all_bfds
<535581c> DW_AT_decl_file : 186
<535581d> DW_AT_decl_line : 58
<535581e> DW_AT_decl_column : 15
<535581f> DW_AT_type : <0x5344aaa>
...
[ FWIW, the address used in the DW_AT_location attribute looks correct:
...
$ nm ./gdb-x | grep all_bfds
0000000001fd8be8 b _ZL8all_bfds
... ]
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (4 preceding siblings ...)
2023-07-19 7:16 ` vries at gcc dot gnu.org
@ 2023-07-19 9:03 ` vries at gcc dot gnu.org
2023-07-19 9:55 ` vries at gcc dot gnu.org
` (6 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 9:03 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
Resulting cooked index entry in failing case:
...
[618404] ((cooked_index_entry *) 0x15aeac00)
name: all_bfds
canonical: all_bfds
DWARF tag: DW_TAG_variable
flags: 0x2 [IS_STATIC]
DIE offset: 0x14fc06f
parent: ((cooked_index_entry *) 0)
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (5 preceding siblings ...)
2023-07-19 9:03 ` vries at gcc dot gnu.org
@ 2023-07-19 9:55 ` vries at gcc dot gnu.org
2023-07-19 10:07 ` vries at gcc dot gnu.org
` (5 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 9:55 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #6)
> Resulting cooked index entry in failing case:
Same for passing case.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (6 preceding siblings ...)
2023-07-19 9:55 ` vries at gcc dot gnu.org
@ 2023-07-19 10:07 ` vries at gcc dot gnu.org
2023-07-19 11:03 ` vries at gcc dot gnu.org
` (4 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 10:07 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
I observe the following:
- in set_initial_language we do a lookup of main, which expands the CU
containing the all_bfds decl.
- when setting a breakpoint on new_symbol conditional on sect_off ==
all_bfds def, it doesn't trigger
So, there seem to be two independent problems:
- new_symbol should have been called for the all_bfds def
- the all_bfds decl was not combined with the minimal symbol to get the
address.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (7 preceding siblings ...)
2023-07-19 10:07 ` vries at gcc dot gnu.org
@ 2023-07-19 11:03 ` vries at gcc dot gnu.org
2023-07-19 11:04 ` vries at gcc dot gnu.org
` (3 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 11:03 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #8)
> - the all_bfds decl was not combined with the minimal symbol to get the
> address.
I forgot, this is done for global symbols, and all_bfds is static.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (8 preceding siblings ...)
2023-07-19 11:03 ` vries at gcc dot gnu.org
@ 2023-07-19 11:04 ` vries at gcc dot gnu.org
2023-07-19 11:47 ` vries at gcc dot gnu.org
` (2 subsequent siblings)
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 11:04 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
Looks like a dup of PR25857.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (9 preceding siblings ...)
2023-07-19 11:04 ` vries at gcc dot gnu.org
@ 2023-07-19 11:47 ` vries at gcc dot gnu.org
2023-08-06 14:42 ` vries at gcc dot gnu.org
2023-11-29 15:08 ` jamborm at gcc dot gnu.org
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-07-19 11:47 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #10)
> Looks like a dup of PR25857.
Well, at least the "maint set worker-threads 0" case. With the tentative patch
from that PR we have:
...
$ for n in $(seq 1 10); do gdb -q -batch ./gdb-x -eiex "maint set
worker-threads 0" -ex "print all_bfds"; done
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$1 = (htab_t) 0x0
$ for n in $(seq 1 10); do gdb -q -batch ./gdb-x -ex "print all_bfds"; done
$1 = <optimized out>
$1 = <optimized out>
$1 = (htab_t) 0x0
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
$1 = <optimized out>
...
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (10 preceding siblings ...)
2023-07-19 11:47 ` vries at gcc dot gnu.org
@ 2023-08-06 14:42 ` vries at gcc dot gnu.org
2023-11-29 15:08 ` jamborm at gcc dot gnu.org
12 siblings, 0 replies; 14+ messages in thread
From: vries at gcc dot gnu.org @ 2023-08-06 14:42 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
--- Comment #12 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 15043
--> https://sourceware.org/bugzilla/attachment.cgi?id=15043&action=edit
Testsuite reproducer
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Bug symtab/30650] [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
` (11 preceding siblings ...)
2023-08-06 14:42 ` vries at gcc dot gnu.org
@ 2023-11-29 15:08 ` jamborm at gcc dot gnu.org
12 siblings, 0 replies; 14+ messages in thread
From: jamborm at gcc dot gnu.org @ 2023-11-29 15:08 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30650
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jamborm at gcc dot gnu.org
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2023-11-29 15:08 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-18 11:49 [Bug testsuite/30650] New: [gdb, lto] FAIL: gdb.gdb/python-helper.exp: print all_bfds vries at gcc dot gnu.org
2023-07-18 14:11 ` [Bug symtab/30650] " vries at gcc dot gnu.org
2023-07-18 15:21 ` vries at gcc dot gnu.org
2023-07-18 17:09 ` vries at gcc dot gnu.org
2023-07-19 7:06 ` vries at gcc dot gnu.org
2023-07-19 7:16 ` vries at gcc dot gnu.org
2023-07-19 9:03 ` vries at gcc dot gnu.org
2023-07-19 9:55 ` vries at gcc dot gnu.org
2023-07-19 10:07 ` vries at gcc dot gnu.org
2023-07-19 11:03 ` vries at gcc dot gnu.org
2023-07-19 11:04 ` vries at gcc dot gnu.org
2023-07-19 11:47 ` vries at gcc dot gnu.org
2023-08-06 14:42 ` vries at gcc dot gnu.org
2023-11-29 15:08 ` jamborm 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).