[Bug ld/28844] ld (bfd) segfaults on building efivar-38 with -flto
https://sourceware.org/bugzilla/show_bug.cgi?id=28844 --- Comment #10 from Nick Clifton --- (In reply to Sam James from comment #9) > I can't reproduce with master nor the binutils-2.38 branch, excellent! In which case are you happy if we close this PR ? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28834] incorrect detection of "DWARF error: section .debug_str is larger than its filesize"
https://sourceware.org/bugzilla/show_bug.cgi?id=28834 HectorOron changed: What|Removed |Added CC||hector.oron at gmail dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28834] incorrect detection of "DWARF error: section .debug_str is larger than its filesize"
https://sourceware.org/bugzilla/show_bug.cgi?id=28834 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1 from Nick Clifton --- Hi Joel, Hmmm, compressed strings would indeed cause this of problem. Could you upload the test binary that you are using ? Compressed sections include a field giving their uncompressed size, so it may be possible to make use of that. But a malicious actor could create a corrupt .zdebug_str section with a ridiculously large "real section size" field and then try to trick the application into allocating a huge amount of memory Maybe a simpler solution would be change the heuristic that produces the error message so that it only complains if the .debug_str section is more than 10x the size of the file ? Just how efficient can (zlib based) text compression get these days ? Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28848] [2.38 Regression] ld assertion fail ../../bfd/elf32-arm.c:14807
https://sourceware.org/bugzilla/show_bug.cgi?id=28848 Matthias Klose changed: What|Removed |Added Target||arm-linux-gnueabihf -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28848] New: [2.38 Regression] ld assertion fail ../../bfd/elf32-arm.c:14807
https://sourceware.org/bugzilla/show_bug.cgi?id=28848 Bug ID: 28848 Summary: [2.38 Regression] ld assertion fail ../../bfd/elf32-arm.c:14807 Product: binutils Version: 2.38 Status: NEW Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: doko at debian dot org Target Milestone: --- Created attachment 13947 --> https://sourceware.org/bugzilla/attachment.cgi?id=13947&action=edit test case seen when building a arm-linux-gnueabihf cross compiler with the 2.38 branch: $ ./run.sh arm-linux-gnueabihf-ld.bfd: BFD (GNU Binutils for Ubuntu) 2.37.90.20220130 assertion fail ../../bfd/elf32-arm.c:14807 The assertion there says it's still needed. Unsure what changed for 2.38, compared to 2.37. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28834] incorrect detection of "DWARF error: section .debug_str is larger than its filesize"
https://sourceware.org/bugzilla/show_bug.cgi?id=28834 Guillaume Morin changed: What|Removed |Added CC||guillaume at morinfr dot org -- You are receiving this mail because: You are on the CC list for the bug.
Issue 43545 in oss-fuzz: binutils:fuzz_dwarf: Null-dereference READ in load_separate_debug_files
Updates: Labels: -restrict-view-commit Comment #3 on issue 43545 by sheriffbot: binutils:fuzz_dwarf: Null-dereference READ in load_separate_debug_files https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43545#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 40647 in oss-fuzz: binutils:fuzz_windres: Null-dereference READ in ubsan_GetStackTrace
Updates: Labels: -restrict-view-commit -deadline-approaching Deadline-Exceeded Comment #4 on issue 40647 by sheriffbot: binutils:fuzz_windres: Null-dereference READ in ubsan_GetStackTrace https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40647#c4 This bug has exceeded our disclosure deadline. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 40670 in oss-fuzz: binutils:fuzz_objcopy: Null-dereference READ in coff_count_linenumbers
Updates: Labels: -restrict-view-commit -deadline-approaching Deadline-Exceeded Comment #4 on issue 40670 by sheriffbot: binutils:fuzz_objcopy: Null-dereference READ in coff_count_linenumbers https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40670#c4 This bug has exceeded our disclosure deadline. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 40892 in oss-fuzz: binutils:fuzz_addr2line: Undefined-shift in place_sections
Updates: Labels: Deadline-Approaching Comment #3 on issue 40892 by sheriffbot: binutils:fuzz_addr2line: Undefined-shift in place_sections https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=40892#c3 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
Issue 43878 in oss-fuzz: binutils:fuzz_readelf: Out-of-memory in fuzz_readelf
Updates: Labels: -restrict-view-commit Comment #3 on issue 43878 by sheriffbot: binutils:fuzz_readelf: Out-of-memory in fuzz_readelf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=43878#c3 This bug has been fixed. It has been opened to the public. - Your friendly Sheriffbot -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.
[Bug binutils/28834] incorrect detection of "DWARF error: section .debug_str is larger than its filesize"
https://sourceware.org/bugzilla/show_bug.cgi?id=28834 --- Comment #2 from Joel Hock --- I can't upload the binary, but the uncompressed size (b6e3fb5 in the output below) is correct. This output is from a different, but similar, binary than what was generating the original error message I posted: $ readelf -t mybinary [Nr] Name Type Address OffsetLink Size EntSize Info Align Flags ... [38] .debug_str PROGBITS 07259234 0 01a18720 0001 0 1 [0830]: MERGE, STRINGS, COMPRESSED ZLIB, 0b6e3fb5, 1 A 10x heuristic would have worked in this case, fwiw. Joel -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28849] New: symbol info passed to linker plugin does not include DT_NEEDED shared libraries
https://sourceware.org/bugzilla/show_bug.cgi?id=28849 Bug ID: 28849 Summary: symbol info passed to linker plugin does not include DT_NEEDED shared libraries Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: ld Assignee: unassigned at sourceware dot org Reporter: sandra at codesourcery dot com Target Milestone: --- Created attachment 13948 --> https://sourceware.org/bugzilla/attachment.cgi?id=13948&action=edit test case script, invoked with compiler pathname as argument The attached test case from Joseph Myers reproduces a bug originally seen by a customer who is trying to use LTO on a much larger application. Working backwards through the symptoms, the error is that LTO is optimizing away the definition of should_be_dynamic_in_exec. It is doing that because ld is passing incorrect symbol resolution info to the LTO plugin and it doesn't know that symbol is referenced externally. And it's getting incorrect symbol resolution info because plugin_call_all_symbols_read() is getting called before the ELF emulation's after_open hook adds DT_NEEDED dependencies to the link. Judging by the comments in the code (lang_process() in ldlang.c), this ordering was deliberate. My idea for fixing this is to split the add-more-files-to-the-link part of the after_open hook into a separate hook that runs both before handing things off to the plugin, and after in case the plugin has added its own new things to the link with further library dependencies. The new hook would have to be idempotent (I suspect the other things the after_open hook may be doing are not). But, I don't have much background on the plugin API... is this a reasonable approach to solving the problem, or is there a better idea I should pursue instead? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/28849] symbol info passed to linker plugin does not include DT_NEEDED shared libraries
https://sourceware.org/bugzilla/show_bug.cgi?id=28849 sandra at codesourcery dot com changed: What|Removed |Added CC||joseph at codesourcery dot com, ||sandra at codesourcery dot com -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/28851] New: ar: add 'L' modifier as a shortcut for ADDLIB
https://sourceware.org/bugzilla/show_bug.cgi?id=28851 Bug ID: 28851 Summary: ar: add 'L' modifier as a shortcut for ADDLIB Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: i at maskray dot me Target Milestone: --- `ar r a.a b.a` adds b.a as a member. Sometimes the user wants to add the members of an archive into another archive. https://sources.debian.org/src/x265/3.5-2/build/linux/multilib.sh/?hl=29#L27 uses the following to merge several archives into one: ar -M
