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

2024-02-28 Thread amodra at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 Alan Modra changed: What|Removed |Added Assignee|unassigned at sourceware dot org |nickc at redhat dot com

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

2017-10-11 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #13 from Mark Wielaard --- (In reply to Tom Tromey from comment #4) > (In reply to Nick Clifton from comment #2) > > * For completeness sake if nothing else, shouldn't we also be able to > > specify an end address for CU dumping

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

2017-10-11 Thread mjw at fedoraproject dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 Mark Wielaard changed: What|Removed |Added CC|mjw at fedoraproject dot org | -- You are receiving this

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

2017-10-11 Thread mjw at fedoraproject dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 Mark Wielaard changed: What|Removed |Added CC||mjw at fedoraproject dot org ---

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

2017-10-10 Thread tromey at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #11 from Tom Tromey --- (In reply to Nick Clifton from comment #10) > dwarf-mode.el:186:6:Warning: set-keymap-parent called with 1 argument, but > requires 2 > > I am not an emacs expert, but maybe this could be a problem

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

2017-10-10 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #10 from Nick Clifton --- Hi Tom, > Thread starts here: > > https://sourceware.org/ml/binutils/2017-10/msg00082.html All the changes look fine to me, apart from one. Patch 2/5 has: +(defvar dwarf-mode-map + (let ((map

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

2017-10-10 Thread tromey at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #9 from Tom Tromey --- Thread starts here: https://sourceware.org/ml/binutils/2017-10/msg00082.html -- 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

2017-10-10 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #8 from Nick Clifton --- Hi Tom, > https://sourceware.org/bugzilla/show_bug.cgi?id=22249 > I will look, but I'd appreciate it if you could look at the dwarf-mode.el > patches that I also posted to the list. Alan had already

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

2017-10-10 Thread tromey at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #7 from Tom Tromey --- (In reply to Nick Clifton from comment #6) > Hi Tom, > > OK, well your patch is fine, so I have checked that in. I still think > that we need to improve the documentation however. Do you have any >

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

2017-10-10 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #6 from Nick Clifton --- Hi Tom, OK, well your patch is fine, so I have checked that in. I still think that we need to improve the documentation however. Do you have any suggestions ? Cheers Nick -- You are receiving

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

2017-10-10 Thread cvs-commit at gcc dot gnu.org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ae7e78255666733d238e676a0bab14986a1483dd commit

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

2017-10-09 Thread tromey at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #4 from Tom Tromey --- (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

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

2017-10-09 Thread mark at klomp dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 Mark Wielaard changed: What|Removed |Added CC||mark at klomp dot org --- Comment #3

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

2017-10-09 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 Nick Clifton changed: What|Removed |Added Status|NEW |ASSIGNED CC|

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

2017-10-06 Thread tromey at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=22249 --- Comment #1 from Tom Tromey --- I think it's as easy as: diff --git a/binutils/dwarf.c b/binutils/dwarf.c index 7ded1bf..f9c93ae 100644 --- a/binutils/dwarf.c +++ b/binutils/dwarf.c @@ -2666,6 +2666,13 @@ process_debug_info (struct