The libebt library provides a clean way of getting human-readable backtrace messages in C++. It uses the RAII (resource acquisition is initialisation) idiom to manage backtrace stack items without needing macros, control structures or an external debugger -- adding context to a function or block is done through a single simple variable declaration.
http://libebt.berlios.de/
I am not really convinced but it might interest some of you
libebt: get human-readable backtrace messages in C++
libebt: get human-readable backtrace messages in C++
Damien Gerard
Ta3d & Yuni Developer
Ta3d & Yuni Developer
- zuzuf
- Administrateur - Site Admin
- Posts: 3281
- Joined: Mon Oct 30, 2006 8:49 pm
- Location: Toulouse, France
- Contact:
TA3D used a similar system a long time ago, it was removed because it was useless:
_crashes would happen in small critical functions that could not afford such an overhead
_because of overhead it was not used in critical stuffs
so it was dropped, gdb is much more helpful for debugging and pertinent logs are better for end user experience.
_crashes would happen in small critical functions that could not afford such an overhead
_because of overhead it was not used in critical stuffs
so it was dropped, gdb is much more helpful for debugging and pertinent logs are better for end user experience.
=>;-D Penguin Powered
Who is online
Users browsing this forum: No registered users and 5 guests