"Gordon McMillan" <gmcm@hypernet.com> writes: > There is some strangeness to exceptions, Linux, gcc > and linking. In scxx (my minimalist C++ / Python > interface), there's no separate .so involved - the > scxx code is compiled in with the extension. There > are no statics involved, so C linkage works (you don't > need a relinked Python). At a certain gcc release, > exceptions thrown and caught at the top level stopped > working (abort). I think Tim's analysis is right: If it fails every time, there is some conceptual problem somewhere - this one sounds like a bug in gcc, which might fail to emit exception regions correctly or some such (I think I recall one such bug in g++). If it sometimes fails, sometimes "succeed", it rather sounds like memory corruption. I can well imagine how memory corruption could affect RTTI: either the vtable pointer in an object gets overwritten, or the RTTI objects themselves get overwritten. 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