Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-11-10 Thread Petr Salinger
reopen 481543 tags 481543 -moreinfo, -unreproducible found 481543 2.7-16 thanks I installed current gcc-snapshot (and upgraded glibc) on otherwise lenny system, even compiled with gcc-snapshot still runs fine: Target: x86_64-linux-gnu gcc version 4.4.0 20081023 (experimental) [trunk revision 14

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-11-10 Thread Jim Meyering
Petr Salinger <[EMAIL PROTECTED]> wrote: >> This demonstrates that it is indeed a.out/libc that provokes >> the segfault. Here's the output I get: >> >>[2331489.137491] zsh[21289]: segfault at 0 ip 7f1126c824f4 sp \ >> 7fff2fa49778 error 6 in libc-2.7.so[7f1126c06000+14a000] >> >> Do the

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-11-10 Thread Petr Salinger
This demonstrates that it is indeed a.out/libc that provokes the segfault. Here's the output I get: [2331489.137491] zsh[21289]: segfault at 0 ip 7f1126c824f4 sp \ 7fff2fa49778 error 6 in libc-2.7.so[7f1126c06000+14a000] Do the same thing with true, and there's no problem: $ env -u

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-11-10 Thread Jim Meyering
Petr Salinger <[EMAIL PROTECTED]> wrote: > could you test what are exactly condition of segfault ? > > For me (glibc 2.7-15, x86_64) > strace zsh -c 'ulimit -v 1; strace ./a.out %$[5*2**25]d' > segfaults, but > strace zsh -c 'ulimit -v 1; ./a.out %$[5*2**25]d' > does not. > > Similarly

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-11-10 Thread Petr Salinger
Please, could you test what are exactly condition of segfault ? For me (glibc 2.7-15, x86_64) strace zsh -c 'ulimit -v 1; strace ./a.out %$[5*2**25]d' segfaults, but strace zsh -c 'ulimit -v 1; ./a.out %$[5*2**25]d' does not. Similarly with "ulimit -v 5000", it looks like strace wit

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-11-09 Thread Jim Meyering
Hi Aurelian, Sorry about the lack of response. I never saw your replies, and only noticed (on the web) today that the bug is now closed due to lack of feedback. The email address for me that was used in that bug report is invalid. The one above works. I can still reproduce the problem on an x86

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-07-22 Thread Aurelien Jarno
Aurelien Jarno a écrit : > tag 481543 + unreproducible > tag 481543 + moreinfo > thanks > > On Fri, May 16, 2008 at 10:30:34PM +0200, Jim Meyering wrote: >> Package: libc6 >> Version: 2.7-11 >> Severity: normal >> >> glibc's snprintf function malfunctions (segfault) >> when its internal memory all

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-06-02 Thread Aurelien Jarno
tag 481543 + unreproducible tag 481543 + moreinfo thanks On Fri, May 16, 2008 at 10:30:34PM +0200, Jim Meyering wrote: > Package: libc6 > Version: 2.7-11 > Severity: normal > > glibc's snprintf function malfunctions (segfault) > when its internal memory allocation fails. > FYI, this bug is new in

Processed: Re: Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-06-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tag 481543 + unreproducible Bug#481543: libc6: low-memory snprintf provokes internal segfault There were no tags set. Tags added: unreproducible > tag 481543 + moreinfo Bug#481543: libc6: low-memory snprintf provokes internal segfault Tag

Bug#481543: libc6: low-memory snprintf provokes internal segfault

2008-05-16 Thread Jim Meyering
Package: libc6 Version: 2.7-11 Severity: normal glibc's snprintf function malfunctions (segfault) when its internal memory allocation fails. FYI, this bug is new in libc6 2.7-11. I noticed because it provokes a new failure in coreutils' printf-surprise test. This is not a problem when using rawh