Hi,
I have a problem where catch blocks are being ignored when exceptions are
thrown from within try blocks. In just about all of these cases the call
stack at fault will originate from the QNX socket library. I have tried
linking this library in various ways, but to no avail. Exceptions work in
the normal course of things but not here. Has anyone come across anything
like this or is anyone able to shed light on the problem?
Thanks
Dave
Here’s one possiblity: After the exception has occurred, as the stack is
being unravelled to get you out of your try block, objects created on the
stack within that try block are being deleted, and a second exception occurs
inside one of these destructors. In this case you don’t make it to your
catch block.
“David Shepherd” <ovioprime@N!O!S!P!A!Myahoo.com> wrote in message
news:ckioc2$3p2$1@inn.qnx.com…
Hi,
I have a problem where catch blocks are being ignored when exceptions are
thrown from within try blocks. In just about all of these cases the call
stack at fault will originate from the QNX socket library. I have tried
linking this library in various ways, but to no avail. Exceptions work in
the normal course of things but not here. Has anyone come across anything
like this or is anyone able to shed light on the problem?Thanks
Dave
David Shepherd wrote:
Hi,
I have a problem where catch blocks are being ignored when exceptions are
thrown from within try blocks. In just about all of these cases the call
stack at fault will originate from the QNX socket library. I have tried
linking this library in various ways, but to no avail. Exceptions work in
the normal course of things but not here. Has anyone come across anything
like this or is anyone able to shed light on the problem?Thanks
Dave
What version of QNX?
What target platform?
sample code? QCC options?
The socket lib does not generate exceptions, and to my knowledge
doesn’t call out to user code. So I don’t know how the call stack could
have originated there…