strings: clarify 8/16 bit
You should put the bug address (back?) on the man page. $ man strings `-e ENCODING' `--encoding=ENCODING' Select the character encoding of the strings that are to be found. Possible values for ENCODING are: `s' = single-7-bit-byte characters (ASCII, ISO 8859, etc., default), `S' = single-8-bit-byte characters, `b' = 16-bit bigendian, `l' = 16-bit littleendian, `B' = 32-bit bigendian, `L' = 32-bit littleendian. Useful for finding wide character strings. Mention if e.g., gb2312 is which one: it is pairs of 8 bit chars, = 16 bit? Well only -e S finds any. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
[Bug binutils/2584] SIGSEGV in strings tool when the file is crafted.
--- Additional Comments From kkojima at rr dot iij4u dot or dot jp 2006-04-23 23:44 --- Created an attachment (id=978) --> (http://sourceware.org/bugzilla/attachment.cgi?id=978&action=view) a patch I can reproduce this on CVS too. bfd/tekhex.c:getsym() doesn't check if the length character is a valid hexadecimal character. hex_value() returns 99 for non hexadecimal characters and getsym uses it as the length to be read. Then it causes a buffer overrun because getsym is called with only 17 bytes buffer. The patch attached seems to fix the given test case anyway, though it'd be better to add more checks. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2584 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ bug-binutils mailing list bug-binutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-binutils
