https://sourceware.org/bugzilla/show_bug.cgi?id=34408
Sam James <sam at gentoo dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|build |gprofng
Product|gdb |binutils
Status|UNCONFIRMED |RESOLVED
Target Milestone|--- |2.47
Version|17.2 |unspecified
CC| |sam at gentoo dot org
Resolution|--- |INVALID
--- Comment #1 from Sam James <sam at gentoo dot org> ---
It's intended that one build it as part of binutils or its own package, not as
part of gdb.
Anyway, the fix isn't on the gdb branch because nobody thought to include it
there, though we perhaps could've for completeness:
commit 5f66aee7f4bec7a2d8378034116f5e5c3dc50f41
Author: Andreas Schwab <[email protected]>
AuthorDate: Sat Nov 22 11:29:43 2025 +0100
Commit: Andreas Schwab <[email protected]>
CommitDate: Fri Nov 28 21:46:04 2025 +0100
gprofng: protect against standard library macros
The CALL_UTIL macro can expand to an unparsable expression of the argument
is a macro, like with the new const-preserving standard library macros in
C23.
* gprofng/src/collector_module.h (CALL_UTIL): Add parens to not
expand its argument if it is a function-like macro.
I don't expect a gdb-17.3 release and I don't think we include gprofng in the
gdb tarballs anyway. I think you're only seeing this if you're building from
the git branch.
--
You are receiving this mail because:
You are on the CC list for the bug.
