Bug#728953: strtod: Valgrind reports invalid read when first char is 'n' (in the x86_64 version)

2014-02-23 Thread Alessandro Ghedini
On gio, nov 07, 2013 at 11:07:00 +0100, Boris D. Carlsson wrote: Package: libc6 Version: 2.13-38 Severity: minor When strtod receives a string starting with 'n', it will read 16 bytes regardless of the actual length of the string sent. Example: $ echo #include stdlib.h int main() {

Bug#728953: strtod: Valgrind reports invalid read when first char is 'n' (in the x86_64 version)

2014-02-22 Thread Aurelien Jarno
reassign 728953 valgrind thanks On Thu, Nov 07, 2013 at 11:07:00AM +0100, Boris D. Carlsson wrote: Package: libc6 Version: 2.13-38 Severity: minor When strtod receives a string starting with 'n', it will read 16 bytes regardless of the actual length of the string sent. strtod calls

Bug#728953: strtod: Valgrind reports invalid read when first char is 'n' (in the x86_64 version)

2013-11-07 Thread Boris D. Carlsson
Package: libc6 Version: 2.13-38 Severity: minor When strtod receives a string starting with 'n', it will read 16 bytes regardless of the actual length of the string sent. Example: $ echo #include stdlib.h int main() { char buf[] = no; strtod(buf, NULL); } main.c $ gcc main.c $