http://bugzilla.novell.com/show_bug.cgi?id=540647 http://bugzilla.novell.com/show_bug.cgi?id=540647#c21 Michael Matz <matz@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz@novell.com Severity|Normal |Major --- Comment #21 from Michael Matz <matz@novell.com> 2009-12-02 10:52:09 UTC --- Hmpf. I can make it crash in STABLE too (glibc 2.10.1), on x86-64, but it doesn't crash or give any errors under valgrind. The crash itself is in: #0 malloc_consolidate (av=0x7f4eef370e60) at malloc.c:5111 #1 0x00007f4eef08f3d4 in _int_malloc (av=0x7f4eef370e60, bytes=1920) at malloc.c:4360 #2 0x00007f4eef091a79 in __libc_malloc (bytes=1920) at malloc.c:3660 I.e. glibc's internal malloc structures are barfed. Normally I would say that its probably some buffer overflow in nano, but as valgrind doesn't have to say anything interesting, this is hard to detect. MALLOC_CHECK_=1 or linking with -lmcheck just changes the point of segfault. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.