[Bug binutils/29505] xxx-w64-mingw32-objdump takes a long time to scan pe binaries for debug information

[ralf.habacker at freenet dot de]

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

--- Comment #4 from Ralf Habacker <ralf.habacker at freenet dot de> ---
(In reply to Ralf Habacker from comment #3)

> Looking at the the valgrind backtrace, the commit 
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;
> h=9f272209118972864b2c3799ddf2b39683c1a7b7 may be related to this issue as
> it changes the affected location in read_and_display_attr_value(). 
> 

The memory leak seems to be fixed by the recently added commit
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=450da4bd38ae529a6879baafe59b1e88507b5fd9

> (process_debug_info): Use it when before clearing out unit
> debug_information.  Clear all fields.

which is confirmed by valgrind
...
==5627== Command:
/home/osc/build-root/openSUSE_Leap_15.3-x86_64/home/abuild/rpmbuild/BUILD/binutils-2.39/build/binutils/objdump
-Wi
/home/xxx/Downloads/usr/i686-w64-mingw32/sys-root/mingw/bin/assistant-qt5.exe.debug
==5627== 
==5627== 
==5627== HEAP SUMMARY:
==5627==     in use at exit: 0 bytes in 0 blocks
==5627==   total heap usage: 739,275 allocs, 739,275 frees, 125,827,392,706
bytes allocated
==5627== 
==5627== All heap blocks were freed -- no leaks are possible

I'm going to rebuild binutils 2.39 with this commit and will check if the
performance issue is also fixed.

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