If a constructor crashes, the the object that it was constructing will be destroyed. (fpc inserts an exception frame to ensure that).

So far so good, all correct.

But if the destructor (e.g Destroy) also crashes, then if you have -gl it will dump the stack for the destructor.
The stack for the constructor is never there a way to make it dump the constructor crash as well (maybe before calling destroy)?

fpc trunk (yesterday) / -gl -gw / w32

Martin

Martin wrote

But if the destructor (e.g Destroy) also crashes, then if you have - gl it will dump the stack for the destructor. The stack for the constructor is never 's because backtraces are only dumped when an exception is not

caught. Otherwise you'd probably see a lot backtrace being printed during an average Lazarus run.

Is there a way to make it dump the constructor crash as well (maybe before calling destroy)?

By adding your own try/except code and manually dumping the backtrace.

Jonas

Jonas Maebe wrote

> Is there a way to make it dump the constructor crash as well (maybe > before calling destroy)? By adding your own try/except code and manually dumping the backtrace.

As I remember D2007 has a new feature to store inner exception inside the try-except block.

If you want I can search for the references.

Best regards,
Paul Ishenin.