On Sun, Sep 16, 2012 at 09:34:05AM -0700, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: > On Sun, 16 Sep 2012, Tom Russo wrote: > > > You might try reconfiguring and rebuilding Xastir with the following: > > /path/to/xastir/configure CFLAGS="-O0 -g -fno-inline" > > make && sudo make install > > > > and when it segfaults use "gdb" to figure out where it's crashing. > > Can also try the "xastir -v4095 2>&1 >xastir-debug.log" trick. That will > turn on all debugging and write everything out to a file. Look through the > file to see if there are additional hints about how/where it crashed.
That has the potential of being misleading, if the crash happens nowhere near a debugging output statement. Better than nothing, but not great. If a precompiled binary has these problems, then the best approach, IMHO, is to pitch it and start from a custom compile. Already, the binary is known to have been compiled against different db headers than the libraries, and may have issues with libgeotiff/proj.4 (given the GetDefn failure). I would suspect a bad build right there. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
