I'm still on the go, but fired up an x86 EC2 instance running Ubuntu 12.04 LTS, and the problem also occurs there.
Backtraces look like stack corruption: --- Program received signal SIGSEGV, Segmentation fault. 0xbffff0e0 in ?? () (gdb) bt #0 0xbffff0e0 in ?? () #1 0x00441f0f in ?? () #2 0x0cec8300 in ?? () #3 0x07d588a1 in ?? () #4 0x24048908 in ?? () #5 0xfed3b0e8 in ?? () #6 0x8601b1ff in ?? () #7 0xc4832648 in ?? () --- No idea what is actually going on here (related to exception unwinding?) Need to further investigate this later today. I still wonder what we should do about this concerning the release… Package a LLVM 3.2-based version? David On Fri, Dec 7, 2012 at 1:05 AM, David Nadlinger <[email protected]> wrote: > On Thu, Dec 6, 2012 at 5:34 PM, David Nadlinger <[email protected]> wrote: >> Not sure what the best way going forward here is? > > Just using -O2 instead of -O3 on pre-3.2 seemed to do the trick. But > while my local tests and the new multilib builds on ci.lycus.org pass, > the Travis builds are still failing. > > Need to reactivate my actual 32 bit VMs for testing, I suppose. > > David --
