Oppolzer - Informatik / Blog

Am 22.01.2015 um 18:13 schrieb C.M.:
> I am catching a bad_alloc exception in a catch() block. I call CEE3DMP but
> the stack has been unwound

Really?

If I have a similar situation for example with PL/1, where an exception is
caught by a PL/1 ON ERROR UNIT, I get a traceback which looks like that:

CEEDUMP  called by
ON ERROR unit  called by
some LE error handling stuff  called by
the routine getting the exception (with the CIB)  called by
PL/1 main (for example)  called by
LE initialization stuff.

that is, the stack at the time of the ON ERROR unit still contains the routine
with the exception. So I have no problem seeing the routine that caused the
error. I guess: signal handling in C will do the same.

Is the try/catch logic in C++ that different?

Kind regards

Bernd


> and there is no useful traceback information. So
> I know a new failed, but I have no clue which one. (Well, actually, I do
> know, but let's assume this were an unexpected error occurring at a customer
> site.) Is there any way to determine where (line number, say, and function
> or source module name) the exception occurred?
>
> Does a CIB as obtained by a call to CEE3CIB and declared in leawi.h contain
> anything useful? Or ... ?
>
> Thanks,
>
> C.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to listserv@listserv.ua.edu with the message: INFO IBM-MAIN
>