[Xastir-dev] Another segmentation fault

[Jack Twilley]

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

Here's the backtrace:

(gdb) bt
#0  0x28ecb40c in strcmp () from /lib/libc.so.5
#1  0x0804f9f5 in alert_match (alert=3D0x8927474, match_level=3DALERT_FROM)
    at alert.c:645
#2  0x0804fc14 in alert_active (alert=3D0x8927474, match_level=3DALERT_FROM)
    at alert.c:787
#3  0x0804fea2 in alert_on_screen () at alert.c:936
#4  0x080a1bdf in UpdateTime (clientData=3D0x8586400, id217025404)
    at main.c:9332
#5  0x28398b6e in DoOtherSources () from /usr/X11R6/lib/libXt.so.6
#6  0x28398e2e in XtAppNextEvent () from /usr/X11R6/lib/libXt.so.6
#7  0x2838d98c in XtAppMainLoop () from /usr/X11R6/lib/libXt.so.6
#8  0x080b9a7a in main (argc=3D2, argv=3D0xbfbfeb94) at main.c:25598
#9  0x0804ed82 in _start ()

The last two lines of my TNC log were:

KF6HJO*>WIDE2>APS221:}HNXNPW>APRS,TCPIP,KF6HJO*:;HNXN0629z*161200z3613.20N\=
11946.20W{Center DENSE_FOG {G6TAA
KF6HJO*>WIDE2>APS221:}HNXNPW>APRS,TCPIP,KF6HJO*::NWS_ADVIS:161200z,DENSE_FO=
G,CAZ89>92 {G6TAB

That section of alert.c deals with cancelled alerts.  The first
portion of the conditional of the if statement surrounding line 645
checks to see if alert->alert_level is equal to 'C'.  When I looked at
the variable alert->alert_level in the debugger, it was equal to -48,
which is a sign that the memory allocated to alert was freed.

Curt, if you need me to do more here, just ask.  I figure that by this
part of the message, you've already identified exactly what's wrong. :-)
However, if there's more research to be done to give you more data,
just ask.

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/3rb+GPFSfAB/ezgRAu7+AJ9n4/etFfo6GD2J3DuV330m5FR5fwCggAHq
BaSNLgqm5fKg0XlGx+A2ZuA=3D
=3DjveQ
=2D----END PGP SIGNATURE-----