https://sourceware.org/bugzilla/show_bug.cgi?id=29505
--- Comment #3 from Ralf Habacker <ralf.habacker at freenet dot de> --- (In reply to Nick Clifton from comment #2) Hi Nick, > Please could you upload a copy of the bin/assistant.exe file so that I can > take a look ? The file is bigger than the 100k limit for adding attachments, so I can point you to an rpm archive where the requested file is included. Please search for `qttools-src-debug` at https://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Leap_15.3/noarch/, unpack the archive and see the file usr/i686-w64-mingw32/sys-root/mingw/bin/assistant-qt5.exe.debug inside the archive. > (I assume that this file demonstrates the slowness of objdump yes, when running the related commands in a chroot environment as reported. > as well it leaking memory). yes, also on the host > Is this a regression in performance compared to earlier binutils releases ? The usage of objdump for scanning binaries has been introduced recently, so there are no related information available > Plus is the 2.39 release any better than the 2.38 release ? no, there is no difference with binutils 2.39 $ /home/xxx/Downloads/usr/i686-w64-mingw32/bin/objdump -v GNU objdump (GNU Binutils) 2.39 > The memory leaks point a finger at the DWARF attribute parsing code, but I > suspect that more investigation will be needed to really narrow down the > problem. 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(). Cheers Ralf -- You are receiving this mail because: You are on the CC list for the bug.
