On 3 Nov 2009, [email protected] wrote: > Hey all, > > I have encountered a crash that I find rather perplexing, seemingly in > iso3166.c:
I have had preplexing problems as well with stack traces. I find this method gives the best stack traces with '-02' (which will be the default). ./gtk-gnutella --log-stderr err --log-stdout log --pause-on-crash I run a 'topless' version on i386 debian for days and never get this crash. However, now that I think about it, I configure with '-U d_enablenls' to disable multi-lingual support. Anyways, the '--pause-on-crash' option gives better stack traces than a core file at least for me. Perhaps you already do this? I haven't run gtkg for a few days because I was intending to install a new un-encrypted hard drive to increase performance... but I have been putting that off so I will run the current head. I am guessing that you are gtk2 and did you do a full build? It is possible that something is amiss with an incremental build; especially if you update often and I think you had a time change like me. fwiw, Bill Pringlemeir. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) 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/devconference _______________________________________________ gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
