The problem has finally been pinpointed, thanks Zaxo, tye and broquaint for their suggestions.
It turned out that the problem was in the library's C++ code. Internally, exceptions are caught using
try {...} catch(...) {...}
In the catch, an error code is set, which is subsequently tested in the calling code (via a macro expansion) so that an exception is thrown (just
don't ask, it's not my code). The problem is that in the original
catch some logging is done which... yeah, right, generates an error and hence
some exception is thrown that only got caught in the
catch(...) of my XS code, completely bypassing the intended exception throwing/catching mechanism.
Lessons learned:
- exceptions are handled as one would expect in this setup (NT, ActiveState Perl, MSVC++),
- never ever trust someone who says he tested his code (his test may be succesful, but simply not adequate to find the real problem).
Thanks again to all who helped, -gjb-
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.