[Xastir] Xastir shutting down prematurely

[Curt, WE7U]

On Mon, 18 Mar 2013, Tom Russo wrote:

> There is not such a setting, but if shutting off the igate fixes the issue,
> then you may have found a bug in Xastir.  Pinning it down might be difficult,
> as it would probably be an issue that is only triggered by some incoming
> packet.  You would have to turn on igate logging, and hope that when the code
> crashes, it does so *AFTER* printing data to the igate log.  If it does, then
> it is possible that one could reproduce the failure by feeding the last
> data in the log file back into Xastir somehow.  If you do that, and provide
> the last packet you receive in the igate log before a crash here on the list,
> someone might be able to reproduce the failure and help track down the cause.

One modification:  If it does crash again in this fashion after turning the igate back on, try this instead:

xastir -v2047 2>&1 >~/xastir-crash.log

That will make a LARGE file of all that Xastir does, hopefully catching the error in enough detail if Xastir crashes on you again.

Note that you can't run Xastir in this manner long-term without rolling the file with external programs.  It would fill up your disk over time otherwise.

-- 
Curt, WE7U.        http://wetnet.net/~we7u
The world DOES revolve around me:  I picked the coordinate system!"