https://sourceware.org/bugzilla/show_bug.cgi?id=22249
Bug ID: 22249
Summary: objdump --dwarf-start can be very slow
Product: binutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: tromey at sourceware dot org
Target Milestone: ---
I have a very large debuginfo file.
I'm trying to examine a CU somewhere in the middle to see if there
is a bug in some debuginfo generation.
(See https://github.com/rust-lang/rust/issues/44412 for the gory details)
I wanted to use objdump --dwarf-start, but this is very slow in this
case.
It could be a bit more intelligent by noticing when the start offset
doesn't appear in the current CU -- it could just skip to the next CU.
This would be much faster.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-binutils
