This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: How important is mcheck?
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: gdb at sourceware dot org, Tom Tromey <tromey at redhat dot com>
- Date: Tue, 11 Feb 2014 19:27:37 +0100
- Subject: Re: How important is mcheck?
- Authentication-results: sourceware.org; auth=none
- References: <52F8F53C dot 8090708 at redhat dot com>
On Mon, 10 Feb 2014 16:50:20 +0100, Florian Weimer wrote:
> Could you move mcheck in-tree?
IMO mcheck has been obsoleted by asan (=gcc -fsanitize=address).
I just do not run GDB regularly under asan yet as in that case one can no
longer use 'ulimit -v 1000000' to catch GDB memory runaways.
ERROR: AddressSanitizer failed to allocate 0x400000000 (17179869184) bytes at address 0x00067fff8000 (12)
ReserveShadowMemoryRange failed while trying to map 0x400000000 bytes. Perhaps you're using ulimit -v
Unfortunately 'ulimit -m' (=RSS) has no effect so one has to give up on the
memory limit for GDB. But it should be worth the asan improved checks.
Jan