in gcc you can use this:

#include <execinfo.h>
compile with -g
link with -rdynamic

see here:
http://www.gnu.org/software/libc/manual/html_node/Backtraces.html

I don't know if this is possible in g++

Also I think without a detailed description about how to reproduce a
bug, a backtrace may be not informative enough.


2011/5/28 Roland Häder <r.hae...@gmx.de>

> On Sat, 2011-05-28 at 02:07 +0200, Robert wrote:
> > I think in the Open Source world you should know that you are sending
> > something to someone. But in general backtraces are good if you can deal
> > with them.
> Here is one of these "crash dumps" so you can take a look at it:
>
> http://developer.wz2100.net/attachment/ticket/2730/warzone2100.gdmp-S4AcaK
>
> All info a happy developer need. =)
>
>
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery, 
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now. 
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to