
30 Aug
2006
30 Aug
'06
7:33 p.m.
Tanguy Fautre <tanguy.fautre@spaceapplications.com> writes:
I narrowed the problem a bit.
The problem arise when a boost::python::error_already_set is thrown but never caught (i.e. adding a try/catch block in main() solves the problem).
It seems to me that an uncaught exception should not cause a segfault in Boost.Python. Should it?
No. -- Dave Abrahams Boost Consulting www.boost-consulting.com