https://sourceware.org/bugzilla/show_bug.cgi?id=29505
Bug ID: 29505
Summary: xxx-w64-mingw32-objdump takes a long time to scan pe
binaries for debug information
Product: binutils
Version: 2.38
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: ralf.habacker at freenet dot de
Target Milestone: ---
A speed issue with objdump in conjunction with binaries in portable executable
format (pe) has been noted on https://build.opensuse.org (OBS) and documented
on https://bugzilla.opensuse.org/show_bug.cgi?id=1202431 when run within a
worker on OBS.
The problem can be reproduced in a local chroot environment created with the
osc command line client e.g. with the package at
https://build.opensuse.org/package/show/windows:mingw:win64/mingw64-libqt5-qttools
by running the following commands on an openSUSE Linux system:
# first create an account on OBS if not present, then run:
$ sudo zypper install osc
$ osc -A https://api.opensuse.org checkout
windows:mingw:win64/mingw64-libqt5-qttools && cd $_
$ osc build openSUSE_Leap_15.4 [-j5]
If you examine the timestamps after the term "mingw64-find-debuginfo.sh", you
will get the corresponding values.
The question is whether objdump itself or in conjunction with the binaries used
can cause this problem and if so, how to fix it.
--
You are receiving this mail because:
You are on the CC list for the bug.
