https://sourceware.org/bugzilla/show_bug.cgi?id=17766
--- Comment #2 from Joshua Rogers ---
Is that right?
Isn't the +1 used for the terminating NUL byte?
Thanks,
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-bi
https://sourceware.org/bugzilla/show_bug.cgi?id=17767
--- Comment #1 from Joshua Rogers ---
This is also the case for some FILNMLEN, too.
/binutils-gdb/include/coff/internal.h
470#define FILNMLEN14 /* # characters in a file name */
vs.
/include/coff/pe.h
175#define FILNM
P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: sourceware-bugs at internot dot info
Hi,
In multilpe places, such as peigen.c, a buffer overrun may occur when using
memcpy:
310memcpy (in->x_file.x_fname, ext->x_file.x_fname,
Assignee: unassigned at sourceware dot org
Reporter: sourceware-bugs at internot dot info
Hi,
In pei-x86_64.c, *xdata_name is assigned incorrect memory due to a common error
in handling NUL bytes.
604 char *xdata_name = alloca (strlen (pdata_section->name + 1));
It should
Assignee: unassigned at sourceware dot org
Reporter: sourceware-bugs at internot dot info
Hi,
In /elflink.c, there is a possible invalid bitshift operation in the put_value
function.
In expression x >>= chunksz * 8UL, right shifting by more than 63 bits has
undefined behavio
