On Apr 2, 2007, at 11:27, Curt, WE7U wrote:
Is there something more I can do to help narrow down the cause of
the crash? I have profiling off (because of the large files it
creates) but I can turn it back on if it will help. I have libgc
also off, but I'm sure I can enable it if necessary.
Best would be to run it under a debugger, or else set up your
system so that a crash will cause a crashdump file to be written,
which can then be brought up in a debugger to see where the crash
occurred. This won't always catch what we want though. Your
debugger needs to be thread-aware as Xastir uses multiple threads
(and processes too for that matter). This is pretty serious
developer-type stuff though, so no biggie if you don't want to head
down this path.
Will turning on profiling help? I would be happy to setup a crashdump
or use a debugger if I had any clue how to do such. Any words of
advice would help.
73,
--de Chip (N1MIE) FN41bn
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
