From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-408053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 23009 invoked by alias); 28 Nov 2012 12:32:08 -0000
Received: (qmail 22957 invoked by uid 48); 28 Nov 2012 12:31:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55517] New: [ASAN] ASAN doesn't work with (soft) ulimit on virtual memory
Date: Wed, 28 Nov 2012 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55517-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-11/txt/msg02715.txt.bz2


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

             Bug #: 55517
           Summary: [ASAN] ASAN doesn't work with (soft) ulimit on virtual
                    memory
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rguenth@gcc.gnu.org


The asan runtime should raise any soft limit on virtual memory by the amount
of shadow virtual mappings it creates.  Those are not accounted for in any
limit calculation.

If a hard limit is present it should probably report that instead of failing
with a cryptic message that it cannot allocate memory:
==10720== ERROR: Failed to allocate 0x20000001000 (2199023259648) bytes at
address 0x0ffffffff000 (12)