On 2013-02-18 15:39, Lubos Lunak wrote:
This could be very useful ('catch throw' is so cumbersome in gdb), but I think the first thing to check is if it would actually work. Last time I checked, "recent" features like -fvisibility make backtrace() very often generate call traces that are next to useless. If it turns out the data actually is useful, then also - you can't simply modify the Exception base class, because it's part of the URE, so it should stay binary compatible. It'd need to be stored in the message (which is a question if it's a good or bad idea) or some other way would need to be found. - it'd be good to know how fast/slow the function is. Exceptions generally aren't very fast, but if the function was called every time in the ctor, then depending on fast it is that might make it debug-build-only feature.
Thanks for the feedback. I'll have a go at it and report back. Disclaimer: http://www.peralex.com/disclaimer.html _______________________________________________ LibreOffice mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice
