Re: [cgkit-user] segfault help?

[Matthias B. <mat...@gm...>]

On 13.04.12 07:46, Alejandro Aguilera Martínez wrote:
>> Let me know if this works and I will add this option to the setup script.
> 
> I'm afraid it doesn't work :/
> 
> I added that line to the config file and recompiled the python wrappers,
> but still happens the same. I can see that option in the compiling
> process, for example:
> 
> [...] 
> All the test we did in the last emails give the same thing, seg fault.
> 
> What to do now?

Hm, back to square one then.

Meanwhile I tried compiling my own version of Python and Boost.Python on
Linux (Fedora). I compiled Python 2.6.8 out of the box without any
special configuration and the build options then look similar to the
ones you have, so no -fexceptions option either. But when I build cgkit
against this version, I still don't get the segfault, I just see the
exception as expected.

Maybe let's try to come up with a minimal example that triggers the
segfault, so that it's easier to investigate. I have attached a tiny
extension module (wrapper.cpp) that only has a single function err()
that will throw an exception when it's called with a negative argument.
If you could compile that one (you will have to adjust the paths in
setup.py) and run tst.py (again, you need to adjust the path to the
module) and let me know if this also triggers a segfault or not.

By the way, I could imagine the -fexceptions option had no effect
because the wrapper source files use the suffix *.cpp, so gcc already
knows that this is C++ source code.

- Matthias -