Before, I had wrote that I had trouble getting a decent backtrace from gdb: bt kept crashing the debugger. On the recommendation of some suse forum guy, I upgraded from gdb 6.8.50.20081120 to gdb-6.8.50.20090818. Backtrace works without bull and attached to this message is a stack trace from the crash (when uploading files).
The suse guy gives his explanation of the old gdb's behavior:
>> I think the problem in cplus_demangle_print_callback
>> on some template methods (for instance boost bind calls)
As for the info I attached, interpreting it is beyong me. =(
>From Koen:
>> I did notice however that --db-attach does not work for me neither: I
>> do not think it attaches properly to the process (or valgrind has
>> interfered with it in a way that gdb does not like it).
Upgrading fixed this for me; maybe your gdb
needs to be upgraded too?
fyi: I was about to post a stack trace from a
core file, the one attached is just as good.
Regards.
shared_ptr assertion.tar.gz
Description: GNU Zip compressed data
------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf
_______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
