Charles-François Natali added the comment: > 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 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21037> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com