[Bug binutils/22249] objdump --dwarf-start can be very slow

[mark at klomp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=22249

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Nick Clifton from comment #2)
>   * According to the documentation the --dwarf-start=N command line option
> (which sets the dwarf_start_die variable) specifies the *number* of the DIE
> at which output should start, not the starting address referenced by the
> DIE.  
> 
>   I think that this may be a mistake in the documentation however, as this
> does not appear to match the behaviour of the code.  Either that, or the
> documentation is correct and the code is wrong.  From the way that the
> documentation is written however, it would appear that the code may be at
> fault.

I made the same observations when a request was made to add similar options to
eu-readelf. There are a couple of other odd corner case behaviours too:
https://sourceware.org/bugzilla/show_bug.cgi?id=22250#c1
I think the documentation could certainly be improved/corrected.
Making it stop at the end of the CU also seems like a good improvement.

-- 
You are receiving this mail because:
You are on the CC list for the bug.