public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "konstantin.s.serebryany at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/55517] [ASAN] ASAN doesn't work with (soft) ulimit on virtual memory
Date: Wed, 28 Nov 2012 12:57:00 -0000	[thread overview]
Message-ID: <bug-55517-4-1wmNiuwzFn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55517-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55517

--- Comment #5 from Konstantin Serebryany <konstantin.s.serebryany at gmail dot com> 2012-11-28 12:56:53 UTC ---
We try to minimize the number of syscalls we make in asan run-time. 
One reason for that is that asan may run in a sanbox which disallows some of
them. (Another is just the code bloat)

Why simply removing all the limits before running asan doesn't work? 
Better warning messages will make it move obvious.


  parent reply	other threads:[~2012-11-28 12:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 12:32 [Bug other/55517] New: " rguenth at gcc dot gnu.org
2012-11-28 12:43 ` [Bug other/55517] " konstantin.s.serebryany at gmail dot com
2012-11-28 12:49 ` rguenth at gcc dot gnu.org
2012-11-28 12:50 ` konstantin.s.serebryany at gmail dot com
2012-11-28 12:53 ` [Bug sanitizer/55517] " rguenth at gcc dot gnu.org
2012-11-28 12:57 ` konstantin.s.serebryany at gmail dot com [this message]
2012-11-28 13:01 ` jakub at gcc dot gnu.org
2012-11-28 13:17 ` kcc at gcc dot gnu.org
2013-05-30 16:55 ` anlauf at gmx dot de
2013-05-31 10:21 ` kcc at gcc dot gnu.org
2013-05-31 10:52 ` kcc at gcc dot gnu.org
2013-10-14 23:16 ` mrs at gcc dot gnu.org
2013-10-15  4:52 ` kcc at gcc dot gnu.org

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=bug-55517-4-1wmNiuwzFn@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).