On 9/22/06, Paul Davis <[EMAIL PROTECTED]> wrote:
I'm NOT very knowledgable as to all the other compilers and the backtrace accessibility.
I've know of a guy that did something with similar functionality but a better implementation.
http://www.slamb.org/svn/repos/trunk/projects/atoms/atoms/debug.cc
This is an implementation of a Backtrace class that can be conditionally included in throw exceptions ( He has it compile conditional )
It does depend on the compiler and system though. Specifically, the header execinfo.h ( Which I assume to be a standard gcc extension ). Although, execinfo might not exist on other platforms or for other compilers.
I'm NOT very knowledgable as to all the other compilers and the backtrace accessibility.
And, its not like you get anything more than you'd get from gdb. So, unless you've got a huge project with at least hundreds of installations and want to implement some sort of automatic backtrace report on crash capability, I don't really see the need.
But, I'll have to agree with the other Paul, wrapping code in try/catch blocks is not the way to go (And is generally a Bad Idea).
Hope that helps,
PaulOn 9/22/06, Paul Pogonyshev <[EMAIL PROTECTED]> wrote:Thomas Metz wrote:
> Inconvenients :
> - a VE_CATCH_RETHROW macro shall be added on all methods / functions
This is practically a killer. No one (I think) will add this, it is way
too inconvenient and intrusive (and I guess also a performance slower.)
Paul
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list
_______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
