From: Joe Flowers <flowers.joseph@gmail.com>
To: dwarves@vger.kernel.org
Subject: Fwd: pahole v1.18 introduced a bug that hangs a product-line build
Date: Fri, 24 Nov 2023 01:03:00 -0500 [thread overview]
Message-ID: <CA+4=ZEPUgCT97cATbd630V5pi1Eha1-nRELu_yC5NwBGcjkUxg@mail.gmail.com> (raw)
In-Reply-To: <CA+4=ZENfu6M3UCfdMfie0oW96y7rfu6pkW25jmp343HeL_gztw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1136 bytes --]
---------- Forwarded message ---------
From: Joe Flowers <joe.flowers@nofreewill.com>
Date: Fri, Nov 24, 2023 at 12:59 AM
Subject: pahole v1.18 introduced a bug that hangs a product-line build
To: <dwarves@vger.kernel.org>
Hello,
We have a product build that hangs at the same place every time because of
a change introduced in pahole.c v1.18. The hang occurs in all versions of
pahole.c since, including the latest. We are using Ubuntu 22.04.3 for
builds.
The attached file
"modified-v1.17-pahole.c-that-works-with-dwarves-v1.18-and-EMCMFirmware-builds_Nov-22-2023-04.tar.bz2"
contains pahole.c v1.17 that has been merged with as many pahole.c v1.18
changes as I could so far and still successfully build our product.
If you diff between that modified v1.17 pahole.c and a pristine unchanged
v1.18 pahole.c file, the bug introduction is somewhere in that difference.
I have attached the file "pahole.c-v1.18-pristine-original-unchanged.rar"
for convenience.
Please help me find the root cause of this hang and a fix for pahole or a
workaround for all future versions of pahole.
Thank you!
Joe
[-- Attachment #1.2: Type: text/html, Size: 1514 bytes --]
[-- Attachment #2: modified-v1.17-pahole.c-that-works-with-dwarves-v1.18-and-EMCMFirmware-builds_Nov-22-2023-04.tar.bz2 --]
[-- Type: application/bzip2, Size: 16664 bytes --]
[-- Attachment #3: pahole.c-v1.18-pristine-original-unchanged.rar --]
[-- Type: application/rar, Size: 20212 bytes --]
parent reply other threads:[~2023-11-24 6:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+4=ZENfu6M3UCfdMfie0oW96y7rfu6pkW25jmp343HeL_gztw@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+4=ZEPUgCT97cATbd630V5pi1Eha1-nRELu_yC5NwBGcjkUxg@mail.gmail.com' \
--to=flowers.joseph@gmail.com \
--cc=dwarves@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).