"Ralf W. Grosse-Kunstleve" <rwgk@cci.lbl.gov> writes: > python -> dlopen ext1.so with statically linked libboost_python.a > python -> dlopen ext2.so with statically linked libboost_python.a That explains a lot of things indeed. It doesn't explain why the exception handling on Linux fails (that should still work fine even with two separate copy of each typeinfo object, IMO), but it gives a clue as to what things may have broken: you get two copies of each global object, and gives you access to both copies. Depending on the exact interaction sequence, it is well possible that all kinds of corruption occur. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4