[C++-sig] preventing boost::python::throw_error_already_set

[Stefan Seefeld]

Leonard Ritter wrote:
>
> searching for __cxa_allocate_exception segfault i got quite a few hits 
> in different projects, of which this wiki entry devotes a whole page 
> to the issue:
>
> http://wiki.fifengine.de/Segfault_in_cxa_allocate_exception
>
> The funny thing is: I never got the problem on a machine with an 
> nVidia driver. The two machines who have the reported error run a 
> virtual video card driver and I'm currently asking for the other one, 
> but I bet it's also pure mesa-based or ATI.

The first thing to do in order to confirm this (or in fact in any case 
to better understand the issue) is to write a minimal complete test case 
exhibiting the error. If you can indeed confirm that *any* exception 
will cause this segfault you have already eliminated boost (and python), 
which should make a further drill-down much easier.

Good luck,

       Stefan


-- 

      ...ich hab' noch einen Koffer in Berlin...