Re: backtrace in exception handler



muppet <scott asofyet org> writes:

You ought to be able to do this quite readily in your own perl code.

Yes, that's all I'm looking at.  (The Glib pod could have some guidance,
if there's an easy answer, or a cross reference to somewhere there is
one :-)

Then again, trapped exceptions are not uncommon, especially when
dealing with lots of files.

Yep.  You'd be tempted to test whether the containing eval is the Glib
main loop one, if that's possible; and assume other evals are traps.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]