[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/29505] xxx-w64-mingw32-objdump takes a long time to scan p

From: ralf.habacker at freenet dot de
Subject: [Bug binutils/29505] xxx-w64-mingw32-objdump takes a long time to scan pe binaries for debug information
Date: Tue, 23 Aug 2022 07:26:43 +0000


--- 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
unpack the archive and see the file
usr/i686-w64-mingw32/sys-root/mingw/bin/assistant-qt5.exe.debug inside the

> (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 
may be related to this issue as it changes the affected location in


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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]