[Xastir] Xastir shutting down prematurely

[Tom Russo]

On Mon, Mar 18, 2013 at 01:18:36PM -0400, we recorded a bogon-computron collision of the <kc4lzn at gmail.com> flavor, containing:
> Not that I haven't seen it before but being this was a newly built
> computer, I really didn't want to accept that I had acquired failed parts
> in this brand new machine.

I would really doubt that the source of this is a hardware problem, especially
since the error reported was a buffer overrun.

That said, since lots of people use Xastir in an igate configuration, whatever 
bug that may be there certainly isn't a commonly observed problem.  There may 
be some station near you that is putting out data that Xastir isn't properly
dealing with.  If that's the case, it can be a challenge to find the problem.


> I stopped the last thing I initiated in Xastir.
> 
> Igate interface.

That is probably the right approach to tracking this down.  Turn off features
you're using until the failure goes away, and you've probably identified the
part of the code with a bug.

> It has been 18 hours since I stopped it and it has not shut down. Is there
> a buffer setting for Igate traffic in Xastir?

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.

> On Sun, Mar 17, 2013 at 10:36 AM, Curt, WE7U <curt.we7u at gmail.com> wrote:
> 
> > On Sun, 17 Mar 2013, John Wilson wrote:
> >
> >  Here is the readout of terminal. Is this memory failure?
> >>
> >
> > That's a reasonable guess.  Another might be overheating of the CPU.
> >  Check your fans/heatsinks and memory.
> >
> > Sometimes I swap the banks of memory to see if the failure happens faster,
> > or slower.  You can sometimes tell which bank of memory is failing that way.
> >
> > --
> > Curt, WE7U.        http://wetnet.net/~we7u
> > The greatest enemy of knowledge is not ignorance, it is the illusion of
> > knowledge.  -Stephen Hawking
> >
> > ______________________________**_________________
> > Xastir mailing list
> > Xastir at lists.xastir.org
> > http://lists.xastir.org/cgi-**bin/mailman/listinfo/xastir<http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir>
> >
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]