Hello,
I posted this a while back, but I have had no response yet.
I have a mixed dll which has to catch standard c++ library exceptions. Now I
understand that when any object is thrown as an exception in managed c++,
it is wrapped as a SEHException class instance. This seems to be the case
with the standard c++ library that is thrown.
It also seems to be the case that if you have a catch statement to catch any
scl exceptions that are thrown and you put this catch statement before the
cls Exception catch, your scl exception will be caught.
The problem is that while I can catch my scl exceptions, they seem to have
been munged in the process of wrapping them in the SEHException. I cannot
inspect the cause of the error by calling the what() function - I get an
'Unknown Exception' message back.
Is there any solution to this problem? Can I set a switch to prevent my scl
exception from being wrapped? I know I can't get anything from the Message
property of the SEHException that wraps my scl exception - all that I see
there is "External component has thrown an exception".
TIA,
--
Akin
aknak at aksoto dot idps dot co dot uk
