[Bug gas/32738] New: Wrong source file in error message when used from within a macro
https://sourceware.org/bugzilla/show_bug.cgi?id=32738 Bug ID: 32738 Summary: Wrong source file in error message when used from within a macro Product: binutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: gas Assignee: unassigned at sourceware dot org Reporter: ad...@tho-otto.de Target Milestone: --- When a macro has an error, the wrong filename is listed in the error message. Example: foo.S: .include "foo.inc" foo foo.inc: .macro foo nnop .endm When compiling, i get the error: foo.S: Assembler messages: foo.S:2: Error: Unknown operator -- statement `nnop' ignored foo.S:3: Info: macro invoked from here The first message is wrong: line number 4 is that from foo.inc, not foo.S This is independent of the cpu type (except that the error message might be slightly different, eg. "no such instruction") -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31956] -Wl,--wrap broken with LTO?
https://sourceware.org/bugzilla/show_bug.cgi?id=31956 Sam James changed: What|Removed |Added See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=24415 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gold/24415] - -Wl,--wrap= incompatible with -flto
https://sourceware.org/bugzilla/show_bug.cgi?id=24415 Sam James changed: What|Removed |Added See Also||https://sourceware.org/bugz ||illa/show_bug.cgi?id=31956 -- You are receiving this mail because: You are on the CC list for the bug.
Re: Issue 398060144: binutils:fuzz_as: Heap-use-after-free in obj_elf_attach_to_group
Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/398060144 Changed Disclosure: → May 23, 2025 ___ Reference Info: 398060144 binutils:fuzz_as: Heap-use-after-free in obj_elf_attach_to_group component: Public Trackers > 1362134 > OSS Fuzz status: New reporter: 87...@developer.gserviceaccount.com cc: am...@gmail.com, bug-binutils@gnu.org, da...@adalogics.com, and 2 more collaborators: co...@oss-fuzz.com type: Vulnerability access level: Limited visibility priority: P2 severity: S2 hotlist: Reproducible, Stability-LibFuzzer, Stability-Memory-AddressSanitizer retention: Component default Disclosure: May 23, 2025 Project: binutils Reported: Feb 22, 2025 Generated by Google IssueTracker notification system. You're receiving this email because you are subscribed to updates on Google IssueTracker issue 398060144 Unsubscribe from this issue.
Issue 398060144: binutils:fuzz_as: Heap-use-after-free in obj_elf_attach_to_group
Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/398060144 Reference Info: 398060144 binutils:fuzz_as: Heap-use-after-free in obj_elf_attach_to_group component: Public Trackers > 1362134 > OSS Fuzz status: New reporter: 87...@developer.gserviceaccount.com cc: am...@gmail.com, bug-binutils@gnu.org, da...@adalogics.com, and 2 more collaborators: co...@oss-fuzz.com type: Vulnerability access level: Limited visibility priority: P2 severity: S2 hotlist: Reproducible, Stability-LibFuzzer, Stability-Memory-AddressSanitizer retention: Component default Project: binutils Reported: Feb 22, 2025 87...@developer.gserviceaccount.com added comment #1: Detailed Report: https://oss-fuzz.com/testcase?key=4713848585650176 Project: binutils Fuzzing Engine: libFuzzer Fuzz Target: fuzz_as Job Type: libfuzzer_asan_binutils Platform Id: linux Crash Type: Heap-use-after-free READ 8 Crash Address: 0x5210e0d0 Crash State: obj_elf_attach_to_group read_a_source_file fuzz_as.h Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_binutils&range=202301110611:202301120617 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4713848585650176 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. This bug is subject to a 90 day disclosure deadline. If 90 days elapse without an upstream patch, then the bug report will automatically become visible to the public. Generated by Google IssueTracker notification system. You're receiving this email because you are subscribed to updates on Google IssueTracker issue 398060144 Unsubscribe from this issue.
