[Bug ld/26404] ld: INSERT [AFTER|BEFORE] variant for extension purposes
https://sourceware.org/bugzilla/show_bug.cgi?id=26404
--- Comment #11 from Fangrui Song ---
My latest revision of https://reviews.llvm.org/D103303 switched to a new
keyword "OVERWRITE_SECTIONS". I dropped the command line option.One can place
more than descriptions, though there is no ordering requirement, e.g.
OVERWRITE_SECTIONS {
.foo.data : { FOO_DATA_START = .; *(.foo.data) FOO_DATA_END = .; }
.foo.text : { FOO_TEXT_START = .; *(.foo.text) FOO_TEXT_END = .; }
}
.foo.data can be after .foo.text .
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug binutils/27965] New: nm-new stuck in infinite loop while damaging rust symbol
https://sourceware.org/bugzilla/show_bug.cgi?id=27965 Bug ID: 27965 Summary: nm-new stuck in infinite loop while damaging rust symbol Product: binutils Version: 2.37 (HEAD) Status: UNCONFIRMED Severity: normal Priority: P2 Component: binutils Assignee: unassigned at sourceware dot org Reporter: terrynini38514 at gmail dot com Target Milestone: --- Created attachment 13485 --> https://sourceware.org/bugzilla/attachment.cgi?id=13485&action=edit damagle loop POC The POC was attached and it can be reproduced in latest version of binutils. The POC cause nm-new stuck in infinite loop at rust-demangle.c:1024 and rust-demangle.c:747 while using the nm-new with option -C. And I want to apply for CVE, if that requires me to do anything more, like attach a valid patch or something ? Please let me know, thanks. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/27965] nm-new stuck in infinite loop while demagling rust symbol
https://sourceware.org/bugzilla/show_bug.cgi?id=27965 terrynini38514 at gmail dot com changed: What|Removed |Added Summary|nm-new stuck in infinite|nm-new stuck in infinite |loop while damaging rust|loop while demagling rust |symbol |symbol -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/27965] nm-new stuck in infinite loop while demangling rust symbol
https://sourceware.org/bugzilla/show_bug.cgi?id=27965 terrynini38514 at gmail dot com changed: What|Removed |Added Summary|nm-new stuck in infinite|nm-new stuck in infinite |loop while demagling rust |loop while demangling rust |symbol |symbol -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/27965] nm-new stuck in infinite loop while demangling rust symbol
https://sourceware.org/bugzilla/show_bug.cgi?id=27965 Alan Modra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |MOVED Assignee|unassigned at sourceware dot org |amodra at gmail dot com --- Comment #1 from Alan Modra --- I've verified that your testcase does cause infinite recursion and a segfault, both with current binutils and with libiberty/rust-demangle.c from gcc, however gcc is the project that owns libiberty. The correct place to report problems in the demangler is https://gcc.gnu.org/bugzilla/. I've marked this bug as moved but will leave it up to you to create a new gcc bug. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/27952] ld: Disallow ET_DYN DF_1_PIE linker input?
https://sourceware.org/bugzilla/show_bug.cgi?id=27952 Alan Modra changed: What|Removed |Added Last reconfirmed||2021-06-08 Assignee|unassigned at sourceware dot org |amodra at gmail dot com Target Milestone|--- |2.37 Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Alan Modra --- Makes sense. -- You are receiving this mail because: You are on the CC list for the bug.
