On Sun, 16 Sep 2012, Tom Russo wrote:
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.
All true.
--
Curt, WE7U. http://wetnet.net/~we7u
APRS Wiki: http://info.aprs.net/
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
