From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: gdb@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: How important is mcheck?
Date: Tue, 11 Feb 2014 18:27:00 -0000 [thread overview]
Message-ID: <20140211182737.GA17519@host2.jankratochvil.net> (raw)
In-Reply-To: <52F8F53C.8090708@redhat.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
prev parent reply other threads:[~2014-02-11 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 15:50 Florian Weimer
2014-02-11 17:05 ` Tom Tromey
2014-02-11 21:28 ` Florian Weimer
2014-02-11 21:44 ` Tom Tromey
2014-02-11 18:27 ` Jan Kratochvil [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140211182737.GA17519@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=fweimer@redhat.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox