[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/22249] objdump --dwarf-start can be very slow
From: |
mjw at fedoraproject dot org |
Subject: |
[Bug binutils/22249] objdump --dwarf-start can be very slow |
Date: |
Wed, 11 Oct 2017 12:13:08 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=22249
Mark Wielaard <mjw at fedoraproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjw at fedoraproject dot org
--- Comment #12 from Mark Wielaard <mjw at fedoraproject dot org> ---
(In reply to Tom Tromey from comment #4)
> (In reply to Nick Clifton from comment #2)
> > I think that this may be a mistake in the documentation however, as this
> > does not appear to match the behaviour of the code.
>
> It is, because the intent (I added this feature initially) was to pass in the
> DIE offset -- I suppose I used the term "number" because DIEs are always
> referred to by offset, so I didn't consider any possible confusion here.
Not every offset is a DIE "number". There is some slight confusion what happens
if the offset is in the middle of a DIE, should it back up and print that one
or should it start printing at the first offset after that is a DIE "number"?
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/22249] objdump --dwarf-start can be very slow, (continued)
- [Bug binutils/22249] objdump --dwarf-start can be very slow, nickc at redhat dot com, 2017/10/09
- [Bug binutils/22249] objdump --dwarf-start can be very slow, mark at klomp dot org, 2017/10/09
- [Bug binutils/22249] objdump --dwarf-start can be very slow, tromey at sourceware dot org, 2017/10/09
- [Bug binutils/22249] objdump --dwarf-start can be very slow, cvs-commit at gcc dot gnu.org, 2017/10/10
- [Bug binutils/22249] objdump --dwarf-start can be very slow, nickc at redhat dot com, 2017/10/10
- [Bug binutils/22249] objdump --dwarf-start can be very slow, tromey at sourceware dot org, 2017/10/10
- [Bug binutils/22249] objdump --dwarf-start can be very slow, nickc at redhat dot com, 2017/10/10
- [Bug binutils/22249] objdump --dwarf-start can be very slow, tromey at sourceware dot org, 2017/10/10
- [Bug binutils/22249] objdump --dwarf-start can be very slow, nickc at redhat dot com, 2017/10/10
- [Bug binutils/22249] objdump --dwarf-start can be very slow, tromey at sourceware dot org, 2017/10/10
- [Bug binutils/22249] objdump --dwarf-start can be very slow,
mjw at fedoraproject dot org <=
- [Bug binutils/22249] objdump --dwarf-start can be very slow, mjw at fedoraproject dot org, 2017/10/11
- [Bug binutils/22249] objdump --dwarf-start can be very slow, mark at klomp dot org, 2017/10/11