On Monday 18 of February 2013, Tom Tromey wrote:
> >>>>> "Lubos" == Lubos Lunak <l.lu...@suse.cz> writes:
>
> Lubos> This could be very useful ('catch throw' is so cumbersome in
> Lubos> gdb),
>
> Is there something we could do to improve it?
I don't know how much control gdb over exception handling has, so I don't
know :).
What I was refering to was the problem that if a catch block catches an
exception, it's often difficult to find out where it actually came from.
Using 'catch catch' doesn't show where it originated (unless I missed a
non-obvious way). And if the exception propagated out of complex nesting of
function calls, then 'catch throw' may trigger a number of times for
exceptions that will be handled elsewhere.
So it would be useful to have some kind of 'catch throw-for-this-catch', or
at least some 'show exception' (mentioned in 'help catch') that would show
where the currently propagating exception started.
--
Lubos Lunak
l.lu...@suse.cz
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
