Getting beatiful gdb backtraces...

[Derek Atkins]

I don't use --enable-debug myself...  But it just works for me :)
Also make sure your supporting libraries (gtk, glib, guile, etc)
have debugging symbols....

-derek

Priit Laes <amd at tt.ee> writes:

> Hello,
>
> I've been trying to get gdb backtraces, but these backtraces look like
> this when using information found in HACKING document.
> [snip]
> #0  0xffffe410 in ?? ()
> #1  0xbfffe2ac in ?? ()
> #2  0x00000006 in ?? ()
> #3  0x000066f3 in ?? ()
> #4  0x40181281 in raise () from /lib/libc.so.6
> #5  0x40182972 in abort () from /lib/libc.so.6
> #6  0x403c9ede in ?? ()
> #7  0x085b5070 in ?? ()
> #8  0x00000006 in ?? ()
> [/snip]
> How do you guys get the nice backtraces I've seen on mailinglist?
>
> My environment information:
> ./autogen.sh --enable-opt-style-install --enable-debug --prefix=/home/
> amd/playground/
> Glibc 2.3.3 with NPTL 0.61
> gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-
> 8.7.6)
> gdb 6.1
> -- 
> Priit Laes <amd tt ee>
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available