[Bug symtab/30727] New: [gdb/symtab] Maintenance command to reverse DIE reading order

[Bug symtab/30727] New: [gdb/symtab] Maintenance command to reverse DIE reading order

[vries at gcc dot gnu.org]

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.

[Bug symtab/30727] [gdb/symtab] Maintenance command to reverse DIE reading order

[tromey at sourceware dot org]

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.

[Bug symtab/30727] [gdb/symtab] Maintenance command to reverse DIE reading order

[vries at gcc dot gnu.org]

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.