[Xastir] Too many crashes

[Jack Twilley]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Jack" =3D=3D Jack Reilly <aa6vn at pacbell.net> writes:

[... mysterious xastir crash after replacing the card ...]

Jack> After restarting it I lost it again in the afternoon. This time
Jack> I got a message : "Caught Segfault! Xastir will terminate Last
Jack> incoming line was: >> 82A0AE646470E0 966C8A9CA24060
Jack> AE6C86B04040E6 AE92888A404060 AE6C84B09C4067 03F0 08:41:50"

Jack> I do not know what a segfault is and cannot find anything on
Jack> it. I started xastir again and this morning it is still running
Jack> ok.

A segfault is a segmentation fault, where xastir attempts to access
some memory but the access goes awry.  This often happens when xastir
accesses memory that was released back to the operating system due to
a bug.

Jack> So far it looks like changing the card has eliminated the X
Jack> crashes but I still cannot keep Xastir running.

I would be interested in hearing more about your interfaces -- what
they are and which ones were open at the time.  I don't know of an
interface type that accepts a huge pile of hexadecimal values, but I
could be wrong.
=20
Jack> Jack aa6vn at pacbell.net

Jack.
=2D --=20
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/22VXGPFSfAB/ezgRApg2AKDsBZEO45QNY3Z/gf5LCUaW3ZyuoACg9iH2
M9jRg6Iv3D9NCj4niTKq6vA=3D
=3DXUCC
=2D----END PGP SIGNATURE-----