Boost Testing :
From: Martin Wille (mw8329_at_[hidden])
Date: 2007-03-28 06:49:45
David Abrahams wrote:
> In fact, these failures look highly suspicious to me. Exit status 139
> indicates a segmentation fault. I haven't seen these tests actually
> /crash/ on any system or compiler before, including all viable
> permutations 32/64-bit linux/windows gcc/msvc. There's definitely
> something very odd going on here; I hope we can clear it up quickly.
I have seen that before when stuff from different compilers or different
Python versions gets mixed.
In this case, we have both. The system's Python 2.3 was compiled with
gcc 3.3.x, while the test's Python 2.4 was compiled with gcc 3.4.x.
However, the test gets run with the system's Python.
Send instant messages to your online friends http://au.messenger.yahoo.com