[Bug binutils/23573] "Too many open files" and binutils 2.31.1-1

https://sourceware.org/bugzilla/show_bug.cgi?id=23573 --- Comment #13 from Benjamin Redelings --- The build directory is about 74Mb compressed, or 38M if I strip out unneeded files. Would there be a good place to upload this? -- You are receiving this mail because: You are on the CC list for

[Bug ld/24730] INCLUDE and --default-script / --script have different whitespace behavior when using REGION_ALIAS

https://sourceware.org/bugzilla/show_bug.cgi?id=24730 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug binutils/23573] "Too many open files" and binutils 2.31.1-1

https://sourceware.org/bugzilla/show_bug.cgi?id=23573 --- Comment #14 from Benjamin Redelings --- I tried running the linker under gdb, but apparently the debian package has stripped out all the debug symbols. Usually you can unstall them in a separate *-dbg package, but I don't see one for the

[Bug binutils/24715] crash in objdump by fuzzing

https://sourceware.org/bugzilla/show_bug.cgi?id=24715 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1

[Bug binutils/23573] "Too many open files" and binutils 2.31.1-1

https://sourceware.org/bugzilla/show_bug.cgi?id=23573 --- Comment #12 from Benjamin Redelings --- Hi Nick, Thanks for the input. So far I've just looked at the strace log that I uploaded, and you are right that archives are getting opened repeatedly. There are three archive filesand they get

[Bug binutils/23573] "Too many open files" and binutils 2.31.1-1

https://sourceware.org/bugzilla/show_bug.cgi?id=23573 Nick Clifton changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED CC|

[Bug binutils/24707] binutils crash invoke files, by using afl fuzzing

https://sourceware.org/bugzilla/show_bug.cgi?id=24707 Nick Clifton changed: What|Removed |Added CC||dlehgo1414 at gmail dot com --- Commen

[Bug binutils/24712] LargerMmapAllocator

https://sourceware.org/bugzilla/show_bug.cgi?id=24712 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug binutils/24710] LargeMmapAllocator (error code: 12)

https://sourceware.org/bugzilla/show_bug.cgi?id=24710 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1

[Bug binutils/24708] Find a [LargeMapAllocator] crash in objdump-2.32 with afl-fuzz

https://sourceware.org/bugzilla/show_bug.cgi?id=24708 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug binutils/24714] crash in objdump by fuzzing

https://sourceware.org/bugzilla/show_bug.cgi?id=24714 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1

[Bug binutils/24708] Find a [LargeMapAllocator] crash in objdump-2.32 with afl-fuzz

https://sourceware.org/bugzilla/show_bug.cgi?id=24708 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7e56c51c7932cfdb178e9457011d09d53e98937b commit 7e56c51c7932cfdb178e9457011

[Bug binutils/24707] binutils crash invoke files, by using afl fuzzing

https://sourceware.org/bugzilla/show_bug.cgi?id=24707 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=781152ec18f56726c750cc0812a740396e4ec820 commit 781152ec18f56726c750cc0812a

[Bug binutils/24707] binutils crash invoke files, by using afl fuzzing

https://sourceware.org/bugzilla/show_bug.cgi?id=24707 Nick Clifton changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug binutils/24706] crashes in objdump when provided with fuzzed linux x86-64 elf samples

https://sourceware.org/bugzilla/show_bug.cgi?id=24706 Nick Clifton changed: What|Removed |Added CC||nickc at redhat dot com --- Comment #1

[Bug ld/23839] ld generates a corrupted relocation table for .ARM.exidx sections

https://sourceware.org/bugzilla/show_bug.cgi?id=23839 --- Comment #12 from lorisnardo at live dot it --- Hi, I have tested the patch with more cases and it works correctly. -- You are receiving this mail because: You are on the CC list for the bug. ___