Issue 50795 in oss-fuzz: binutils:fuzz_dwarf: Direct-leak in bfd_zmalloc

Updates: Labels: -deadline-approaching -restrict-view-commit Deadline-Exceeded Comment #3 on issue 50795 by sheriffbot: binutils:fuzz_dwarf: Direct-leak in bfd_zmalloc https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50795#c3 This bug has exceeded our disclosure deadline. It has bee

Issue 53740 in oss-fuzz: binutils:fuzz_objcopy: Heap-buffer-overflow in bfd_pef_parse_traceback_table

Updates: Labels: -restrict-view-commit Comment #3 on issue 53740 by sheriffbot: binutils:fuzz_objcopy: Heap-buffer-overflow in bfd_pef_parse_traceback_table https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53740#c3 This bug has been fixed. It has been opened to the public. - Your f

[Bug binutils/25202] objcopy --verilog-data-width doesn't respect target's endianness

https://sourceware.org/bugzilla/show_bug.cgi?id=25202 --- Comment #22 from Gökçe Aydos --- I browsed LRM section 21.4 about `$readmemh`, but could not find any info about maximum width (for a memory line that is read by `$readmemh`). I think the range is limited by the maximum width of a vector (