Package: valgrind
Version: 1:3.7.0-6
Severity: normal
Dear Maintainer,
Please consider the following valgrind session:
naesten@hydrogen:~/hacking/bugs% cat stack-overflow.c
/* Stupid stack overflow demo */
int main() {
return main()+1;
}
naesten@hydrogen:~/hacking/bugs% make CFLAGS=-g stack-overflow
cc -g stack-overflow.c -o stack-overflow
naesten@hydrogen:~/hacking/bugs% valgrind ./stack-overflow
==10541== Memcheck, a memory error detector
==10541== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==10541== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==10541== Command: ./stack-overflow
==10541==
==10541== Stack overflow in thread 1: can't grow stack to 0xbe3cbffc
==10541==
==10541== Process terminating with default action of signal 11 (SIGSEGV)
==10541== Access not within mapped region at address 0xBE3CBFFC
==10541== at 0x8048472: main (stack-overflow.c:4)
==10541== If you believe this happened as a result of a stack
==10541== overflow in your program's main thread (unlikely but
==10541== possible), you can try to increase the size of the
==10541== main thread stack using the --main-stacksize= flag.
==10541== The main thread stack size used in this run was 8388608.
==10541== Stack overflow in thread 1: can't grow stack to 0xbe3cbff8
==10541==
==10541== Process terminating with default action of signal 11 (SIGSEGV)
==10541== Access not within mapped region at address 0xBE3CBFF8
==10541== at 0x4021550: _vgnU_freeres (in
/usr/lib/valgrind/vgpreload_core-x86-linux.so)
==10541== If you believe this happened as a result of a stack
==10541== overflow in your program's main thread (unlikely but
==10541== possible), you can try to increase the size of the
==10541== main thread stack using the --main-stacksize= flag.
==10541== The main thread stack size used in this run was 8388608.
==10541==
==10541== HEAP SUMMARY:
==10541== in use at exit: 0 bytes in 0 blocks
==10541== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==10541==
==10541== All heap blocks were freed -- no leaks are possible
==10541==
==10541== For counts of detected and suppressed errors, rerun with: -v
==10541== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 11 from 6)
zsh: segmentation fault valgrind ./stack-overflow
Is it just me, or should valgrind print a stack trace after the
"Stack overflow" message?
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages valgrind depends on:
ii libc6 2.13-37
ii libc6-dbg 2.13-37
Versions of packages valgrind recommends:
ii gdb 7.4.1-3
pn valgrind-dbg <none>
Versions of packages valgrind suggests:
pn alleyoop <none>
ii kcachegrind 4:4.8.4-2
pn valgrind-mpi <none>
pn valkyrie <none>
-- no debconf information
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
