public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
* [Bug symtab/30727] New: [gdb/symtab] Maintenance command to reverse DIE reading order
@ 2023-08-06 14:51 vries at gcc dot gnu.org
2023-08-06 15:04 ` [Bug symtab/30727] " tromey at sourceware dot org
2023-08-06 16:19 ` vries at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2023-08-06 14:51 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30727
Bug ID: 30727
Summary: [gdb/symtab] Maintenance command to reverse DIE
reading order
Product: gdb
Version: HEAD
Status: NEW
Severity: enhancement
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
It could be useful to read a CU in reverse top-level DIE order, turning
backward references into forward references and vice versa.
Likewise for CU reading order, turning backward inter-CU references into
forward inter-CU references.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug symtab/30727] [gdb/symtab] Maintenance command to reverse DIE reading order 2023-08-06 14:51 [Bug symtab/30727] New: [gdb/symtab] Maintenance command to reverse DIE reading order vries at gcc dot gnu.org @ 2023-08-06 15:04 ` tromey at sourceware dot org 2023-08-06 16:19 ` vries at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: tromey at sourceware dot org @ 2023-08-06 15:04 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=30727 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- I may not be understanding properly, but in general I think it's very difficult or impossible to read DIEs in reverse order. When starting from the end there is no indication where a DIE begins. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug symtab/30727] [gdb/symtab] Maintenance command to reverse DIE reading order 2023-08-06 14:51 [Bug symtab/30727] New: [gdb/symtab] Maintenance command to reverse DIE reading order vries at gcc dot gnu.org 2023-08-06 15:04 ` [Bug symtab/30727] " tromey at sourceware dot org @ 2023-08-06 16:19 ` vries at gcc dot gnu.org 1 sibling, 0 replies; 3+ messages in thread From: vries at gcc dot gnu.org @ 2023-08-06 16:19 UTC (permalink / raw) To: gdb-prs https://sourceware.org/bugzilla/show_bug.cgi?id=30727 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Tom Tromey from comment #1) > I may not be understanding properly, but in general I think > it's very difficult or impossible to read DIEs in reverse order. > When starting from the end there is no indication where a DIE begins. My idea was to do a preliminary scan that finds the dies, stores the offsets in a list in reverse order, and use that as the iteration order. -- You are receiving this mail because: You are on the CC list for the bug. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-08-06 16:19 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2023-08-06 14:51 [Bug symtab/30727] New: [gdb/symtab] Maintenance command to reverse DIE reading order vries at gcc dot gnu.org 2023-08-06 15:04 ` [Bug symtab/30727] " tromey at sourceware dot org 2023-08-06 16: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).