Author neologix
Recipients christian.heimes, neologix, pitrou, vstinner
Date 2014-04-29.20:08:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0x9i8Y4G+sdYy6E76YtMPC3G0J79c8iu5M4Uy8qwXBbQ@mail.gmail.com>
In-reply-to <1398758293.99.0.303253903098.issue21037@psf.upfronthosting.co.za>
Content
> That said, it would be better if you first check said options work locally.

I wasn't clear, but I did test it, and it works: the only problem I
encountered is address space exhaustion: I have a 32-bit box, and ASAN
uses a lot of virtual address space (for shadow pages), so with a lot
of memory or many thread you can hit the 3G limit.
So we should only run this on 64-bit machine (see below for more details).

> I can add environment variables and configure options specific to a buildbot. Just tell me which ones (and which buildbot (preferably yours ? :-)).

Yeah, I barely have a day-to-day machine, so I'm afraid I can't help here :-)

I guess we could go for any non-stable buildbot meeting the following criteria:
- Linux 64-bit
- clang >= 3.1 or gcc >= 4.8

But it would be great if someone could test the patch locally on a
64-bit machine before I commit it.
Basically:

$ patch -p1 < ~/asan.diff && autoconf && autoheader && ./configure
--with-address-sanitizer && make
$ ASAN_OPTIONS=handle_segv=0 ./python -m test -vG -uall
History
Date User Action Args
2014-04-29 20:08:22neologixsetrecipients: + neologix, pitrou, vstinner, christian.heimes
2014-04-29 20:08:22neologixlinkissue21037 messages
2014-04-29 20:08:21neologixcreate