[Xastir] Xastir Digest, Vol 60, Issue 8

John Hartman n5aaa at bellsouth.net
Sun Nov 28 11:14:50 EST 2010 

Update - -

The offending station has been off the air and therefore I haven't been
able to isolate the problem further.  When more info is available I will
forward.

John


-----Original Message-----
From: xastir-request at lists.xastir.org
Reply-to: xastir at lists.xastir.org
To: xastir at lists.xastir.org
Subject: Xastir Digest, Vol 60, Issue 8
Date: Sun, 21 Nov 2010 12:00:01 -0500

Send Xastir mailing list submissions to
	xastir at lists.xastir.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
or, via email, send a message with subject or body 'help' to
	xastir-request at lists.xastir.org

You can reach the person managing the list at
	xastir-owner at lists.xastir.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xastir digest..."


Today's Topics:

   1. Received station packets causing Xastir to crash (John Hartman)
   2. Re: Received station packets causing Xastir to crash
      (Lynn W Deffenbaugh (Mr))
   3. Re: Received station packets causing Xastir to crash (Tom Russo)
   4. Re: Received station packets causing Xastir to crash (Tom Russo)


----------------------------------------------------------------------

Message: 1
Date: Sat, 20 Nov 2010 12:03:51 -0600
From: John Hartman <n5aaa at bellsouth.net>
To: xastir at lists.xastir.org
Cc: jthartman at bellsouth.net
Subject: [Xastir] Received station packets causing Xastir to crash
Message-ID: <1290276231.6671.17.camel at ubuntu-jth1>
Content-Type: text/plain; charset="UTF-8"





I am running Ubuntu 10.04 and Xastir 2.0.1 and have a problem with
Xastir crashing after receiving packets from a specific station.   

I discovered this by running Xastir from terminal mode and turning on
the debug level (to 1) in xastir,  The crash always seem to occur right
after processing traffic from a specific station. Is there some setting
I've missed that will let me block this station.  

All help appreciated.  

Is there a way to block the offending station?  

73 John N5AAA

Following is the information captured:
--------------------
APN391,qAR,KF4ERV
APN391

decode_info_field: done
decode_ax25_line: exiting
Channel data on Port 1
[????@@`??h???f????@@`????b at c?=3524.12N/08552.35W#/APRSDIGI DEER RUN,
TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45]
tnc_data_clean: called to clean
KF4TNP-3>APRS,WIDE,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
tnc_data_clean: clean result
KF4TNP-3>APRS,WIDE,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
decode_ax25_line: start parsing
KF4TNP-3>APRS,WIDE,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
        Comparing WIDE to WIDE1-1
c/p/i/o fr pt tp: Registering data KF4TNP-3 APRS,WIDE,WIDE1-1
=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET, 145.450-
PL127.3 WWW.KF4TNP.NET/ 16.9/23:45  T 1 0
decode_info_field: c:KF4TNP-3 p:APRS,WIDE,WIDE1-1
m:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET,
145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45 f:T o:
decode_info_field: Past check
decode_info_field: ok_igate_net can be read
decode_info_field: = (position w/o timestamp)
data_add:
        type: 1
        call_sign: KF4TNP-3
        path: APRS,WIDE,WIDE1-1
        data: 3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
KF4TNP at CHARTER.NET,
145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
        from: T
        port: 1
        origin: 
        third_party: 0
data_add: Found existing station record.
Setting ST_DIRECT for station KF4TNP-3
decode_info_field: done = 1
decode_info_field: ok_igate_net can be read 2
decode_info_field: done with big switch
decode_info_field: ok_igate_net start
Sending out port: 0, type: 1, path: 
Sending to interface:0,
KF4TNP-3>APRS,WIDE,WIDE1-1,N5AAA-1,I:=3524.12N/08552.35W#/APRSDIGI DEER
RUN, TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45

decode_ax25_line: start parsing
KF4TNP-3>APRS,WIDE,WIDE1-1,N5AAA-1,I:=3524.12N/08552.35W#/APRSDIGI DEER
RUN, TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
c/p/i/o fr pt tp: Registering data KF4TNP-3 APRS,WIDE,WIDE1-1,N5AAA-1
=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET, 145.450-
PL127.3 WWW.KF4TNP.NET/ 16.9/23:45  L 0 0
decode_info_field: c:KF4TNP-3 p:APRS,WIDE,WIDE1-1,N5AAA-1
m:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET,
145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45 f:L o:
decode_info_field: Past check
decode_info_field: ok_igate_net can be read
decode_info_field: = (position w/o timestamp)
data_add:
        type: 1
        call_sign: KF4TNP-3
        path: APRS,WIDE,WIDE1-1,N5AAA-1
        data: 3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
KF4TNP at CHARTER.NET,
145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
        from: L
        port: 0
        origin: 
        third_party: 0
data_add: Found existing station record.
decode_info_field: done = 1
decode_info_field: ok_igate_net can be read 2
decode_info_field: done with big switch
decode_info_field: ok_igate_net start
decode_info_field: done
decode_ax25_line: exiting
decode_info_field: done
decode_ax25_line: exiting
Channel data on Port 1
[????@@`??h???f?b???@???b at c?=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45]
tnc_data_clean: called to clean
KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
tnc_data_clean: clean result
KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
decode_ax25_line: start parsing
KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
        Comparing WIDE1-1 to WIDE1-1
*** buffer overflow detected ***: xastir terminated
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x50)[0xe60390]
/lib/tls/i686/cmov/libc.so.6(+0xe12ca)[0xe5f2ca]
/lib/tls/i686/cmov/libc.so.6(+0xe0a08)[0xe5ea08]
/lib/tls/i686/cmov/libc.so.6(_IO_default_xsputn+0x9e)[0xde7afe]
/lib/tls/i686/cmov/libc.so.6(_IO_vfprintf+0x368a)[0xdbe29a]
/lib/tls/i686/cmov/libc.so.6(__vsprintf_chk+0xad)[0xe5eabd]
/lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xe5e9fd]



------------------------------

Message: 2
Date: Sat, 20 Nov 2010 13:37:54 -0500
From: "Lynn W Deffenbaugh (Mr)" <KJ4ERJ at arrl.net>
To: Xastir - APRS client software discussion <xastir at lists.xastir.org>
Subject: Re: [Xastir] Received station packets causing Xastir to crash
Message-ID: <4CE81582.7060407 at arrl.net>
Content-Type: text/plain; charset=UTF-8; format=flowed

It'd be better to get Xastir fixed than to simply block the station.  
I'm wondering if the /APRSDIGI is tripping up the /A= altitude routine?  
Just guessing...

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

John Hartman wrote:
>
>
> I am running Ubuntu 10.04 and Xastir 2.0.1 and have a problem with
> Xastir crashing after receiving packets from a specific station.   
>
> I discovered this by running Xastir from terminal mode and turning on
> the debug level (to 1) in xastir,  The crash always seem to occur right
> after processing traffic from a specific station. Is there some setting
> I've missed that will let me block this station.  
>
> All help appreciated.  
>
> Is there a way to block the offending station?  
>
> 73 John N5AAA
>
> Following is the information captured:
> --------------------
> APN391,qAR,KF4ERV
> APN391
>
> decode_info_field: done
> decode_ax25_line: exiting
> Channel data on Port 1
> [????@@`??h???f????@@`????b at c?=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45]
> tnc_data_clean: called to clean
> KF4TNP-3>APRS,WIDE,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> tnc_data_clean: clean result
> KF4TNP-3>APRS,WIDE,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> decode_ax25_line: start parsing
> KF4TNP-3>APRS,WIDE,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
>         Comparing WIDE to WIDE1-1
> c/p/i/o fr pt tp: Registering data KF4TNP-3 APRS,WIDE,WIDE1-1
> =3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET, 145.450-
> PL127.3 WWW.KF4TNP.NET/ 16.9/23:45  T 1 0
> decode_info_field: c:KF4TNP-3 p:APRS,WIDE,WIDE1-1
> m:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET,
> 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45 f:T o:
> decode_info_field: Past check
> decode_info_field: ok_igate_net can be read
> decode_info_field: = (position w/o timestamp)
> data_add:
>         type: 1
>         call_sign: KF4TNP-3
>         path: APRS,WIDE,WIDE1-1
>         data: 3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> KF4TNP at CHARTER.NET,
> 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
>         from: T
>         port: 1
>         origin: 
>         third_party: 0
> data_add: Found existing station record.
> Setting ST_DIRECT for station KF4TNP-3
> decode_info_field: done = 1
> decode_info_field: ok_igate_net can be read 2
> decode_info_field: done with big switch
> decode_info_field: ok_igate_net start
> Sending out port: 0, type: 1, path: 
> Sending to interface:0,
> KF4TNP-3>APRS,WIDE,WIDE1-1,N5AAA-1,I:=3524.12N/08552.35W#/APRSDIGI DEER
> RUN, TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
>
> decode_ax25_line: start parsing
> KF4TNP-3>APRS,WIDE,WIDE1-1,N5AAA-1,I:=3524.12N/08552.35W#/APRSDIGI DEER
> RUN, TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> c/p/i/o fr pt tp: Registering data KF4TNP-3 APRS,WIDE,WIDE1-1,N5AAA-1
> =3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET, 145.450-
> PL127.3 WWW.KF4TNP.NET/ 16.9/23:45  L 0 0
> decode_info_field: c:KF4TNP-3 p:APRS,WIDE,WIDE1-1,N5AAA-1
> m:=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN KF4TNP at CHARTER.NET,
> 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45 f:L o:
> decode_info_field: Past check
> decode_info_field: ok_igate_net can be read
> decode_info_field: = (position w/o timestamp)
> data_add:
>         type: 1
>         call_sign: KF4TNP-3
>         path: APRS,WIDE,WIDE1-1,N5AAA-1
>         data: 3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> KF4TNP at CHARTER.NET,
> 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
>         from: L
>         port: 0
>         origin: 
>         third_party: 0
> data_add: Found existing station record.
> decode_info_field: done = 1
> decode_info_field: ok_igate_net can be read 2
> decode_info_field: done with big switch
> decode_info_field: ok_igate_net start
> decode_info_field: done
> decode_ax25_line: exiting
> decode_info_field: done
> decode_ax25_line: exiting
> Channel data on Port 1
> [????@@`??h???f?b???@???b at c?=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45]
> tnc_data_clean: called to clean
> KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> tnc_data_clean: clean result
> KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> decode_ax25_line: start parsing
> KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
>         Comparing WIDE1-1 to WIDE1-1
> *** buffer overflow detected ***: xastir terminated
> ======= Backtrace: =========
> /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x50)[0xe60390]
> /lib/tls/i686/cmov/libc.so.6(+0xe12ca)[0xe5f2ca]
> /lib/tls/i686/cmov/libc.so.6(+0xe0a08)[0xe5ea08]
> /lib/tls/i686/cmov/libc.so.6(_IO_default_xsputn+0x9e)[0xde7afe]
> /lib/tls/i686/cmov/libc.so.6(_IO_vfprintf+0x368a)[0xdbe29a]
> /lib/tls/i686/cmov/libc.so.6(__vsprintf_chk+0xad)[0xe5eabd]
> /lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xe5e9fd]
>
> _______________________________________________
> Xastir mailing list
> Xastir at lists.xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>   



------------------------------

Message: 3
Date: Sat, 20 Nov 2010 12:36:12 -0700
From: Tom Russo <russo at bogodyn.org>
To: Xastir - APRS client software discussion <xastir at lists.xastir.org>
Cc: jthartman at bellsouth.net
Subject: Re: [Xastir] Received station packets causing Xastir to crash
Message-ID: <20101120193612.GA66004 at bogodyn.org>
Content-Type: text/plain; charset=us-ascii

On Sat, Nov 20, 2010 at 12:03:51PM -0600, we recorded a bogon-computron collision of the <n5aaa at bellsouth.net> flavor, containing:
> 
> 
> 
> 
> I am running Ubuntu 10.04 and Xastir 2.0.1 and have a problem with
> Xastir crashing after receiving packets from a specific station.   
> 
> I discovered this by running Xastir from terminal mode and turning on
> the debug level (to 1) in xastir,  The crash always seem to occur right
> after processing traffic from a specific station. Is there some setting
> I've missed that will let me block this station.  
> 
> All help appreciated.  
> 
> Is there a way to block the offending station?  

As Jason points out, the *right* thing to do is fix Xastir so it doesn't
crash on this data.  

> Channel data on Port 1
> [????????????@@`??????h?????????f???b?????????@?????????b at c???=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45]
> tnc_data_clean: called to clean
> KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> tnc_data_clean: clean result
> KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> decode_ax25_line: start parsing
> KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
>         Comparing WIDE1-1 to WIDE1-1
> *** buffer overflow detected ***: xastir terminated
[...]
> /lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xe5e9fd]

This is all from the routine "relay_digipeat" which suggests you are running
your Xastir as a relay (WIDE1-1) digipeater.  Unfortunately, 
"Comparing ... to ..." is the last debug statement in that routine and it
does a bunch of stuff afterward, something of which is broken.

Look in the routine "relay_digipeat" in db.c and find the string "Comparing"
around line 18219.  Subsequent to this line are a lot of fprintf(stderr,..)
calls that are all commented out with "//".  You might want to uncomment them
all to narrow down where the crash is actually happening.  

I don't think the guess that the /A is confusing things is right, because
it gets all the way down to relay_digipeat before crashing.  The packet
is fairly long, it's possible there's a hard-coded small buffer somewhere that
is getting overrun.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 "The truth will set you free, but first it will piss you off."




------------------------------

Message: 4
Date: Sat, 20 Nov 2010 20:25:26 -0700
From: Tom Russo <russo at bogodyn.org>
To: John Hartman <jthartman at bellsouth.net>
Cc: 'Xastir - APRS client software discussion'
	<xastir at lists.xastir.org>
Subject: Re: [Xastir] Received station packets causing Xastir to crash
Message-ID: <20101121032526.GA68672 at bogodyn.org>
Content-Type: text/plain; charset=us-ascii

On Sat, Nov 20, 2010 at 07:20:37PM -0600, we recorded a bogon-computron collision of the <jthartman at bellsouth.net> flavor, containing:
> Tom et all,
> 
>  
> 
> I spoke too soon.  Crashed again when processing packets from KF4TNP-3.
> 
>  
> 
> I turned DIGI off completely and have not crashed again. 

That's good, and confirms that it's in the relay_digipeat section of the
code.  But if you try to pin down where this is really happening, you can help 
us fix the bug.  If you have the time to rebuild Xastir with those debugging
lines commented out, it would help next time it crashes.  If we can get it
fixed, you can run as a relay digipeater again. (The station in question, 
though, is not using WIDE1-1 in the recommended manner, because it's using a 
path of WIDE,WIDE1-1 --- a very bad choice.  But that's another matter 
entirely.)

There's clearly a bug, but since you're the only one who's seeing it, it'll
be hard to track down without a little help.

> From: John Hartman [mailto:jthartman at bellsouth.net] 
> Sent: Saturday, November 20, 2010 3:25 PM
> To: 'russo at bogodyn.org'; 'Xastir - APRS client software discussion'
> Subject: RE: [Xastir] Received station packets causing Xastir to crash
> 
>  
> 
> Tom,
> 
>  
> 
> Interesting.  My digi path was set at WIDE1-1.  Changed it to WIDE2-1 and
> the problem seems to have gone away.  
> 
>  
> 
> Thanks for your help.  Perhaps this can be fixed in a future release.
> 
>  
> 
> 73
> 
> John N5AAA
> 
>  
> 
>  
> 
>  
> 
>   _____  
> 
> From: Tom Russo [mailto:russo at bogodyn.org] 
> Sent: Saturday, November 20, 2010 1:36 PM
> To: Xastir - APRS client software discussion
> Cc: jthartman at bellsouth.net
> Subject: Re: [Xastir] Received station packets causing Xastir to crash
> 
>  
> 
> On Sat, Nov 20, 2010 at 12:03:51PM -0600, we recorded a bogon-computron
> collision of the <n5aaa at bellsouth.net> flavor, containing:
> >
> >
> >
> >
> > I am running Ubuntu 10.04 and Xastir 2.0.1 and have a problem with
> > Xastir crashing after receiving packets from a specific station.  
> >
> > I discovered this by running Xastir from terminal mode and turning on
> > the debug level (to 1) in xastir,  The crash always seem to occur right
> > after processing traffic from a specific station. Is there some setting
> > I've missed that will let me block this station. 
> >
> > All help appreciated. 
> >
> > Is there a way to block the offending station? 
> 
> As Jason points out, the *right* thing to do is fix Xastir so it doesn't
> crash on this data. 
> 
> > Channel data on Port 1
> > [????????????@@`??????h?????????f???b?????????@?????????b at c 
> 
>   _____  
> 
> ???=3524.12N/08552.35W#/APRSDIGI DEER RUN, TN
> > KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45]
> > tnc_data_clean: called to clean
> > KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> > TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> > tnc_data_clean: clean result
> > KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> > TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> > decode_ax25_line: start parsing
> > KF4TNP-3>APRS,W1ARN-1*,WIDE1-1:=3524.12N/08552.35W#/APRSDIGI DEER RUN,
> > TN KF4TNP at CHARTER.NET, 145.450- PL127.3 WWW.KF4TNP.NET/ 16.9/23:45
> >         Comparing WIDE1-1 to WIDE1-1
> > *** buffer overflow detected ***: xastir terminated
> [...]
> > /lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xe5e9fd]
> 
> This is all from the routine "relay_digipeat" which suggests you are running
> your Xastir as a relay (WIDE1-1) digipeater.  Unfortunately,
> "Comparing ... to ..." is the last debug statement in that routine and it
> does a bunch of stuff afterward, something of which is broken.
> 
> Look in the routine "relay_digipeat" in db.c and find the string "Comparing"
> around line 18219.  Subsequent to this line are a lot of fprintf(stderr,..)
> calls that are all commented out with "//".  You might want to uncomment
> them
> all to narrow down where the crash is actually happening. 
> 
> I don't think the guess that the /A is confusing things is right, because
> it gets all the way down to relay_digipeat before crashing.  The packet
> is fairly long, it's possible there's a hard-coded small buffer somewhere
> that
> is getting overrun.
> 
> --
> Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
> Tijeras, NM  QRPL#1592 K2#398  SOC#236
> http://kevan.org/brain.cgi?DDTNM
>  "The truth will set you free, but first it will piss you off."
> 
>   _____  
> 
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1153 / Virus Database: 424/3268 - Release Date: 11/20/10
> 

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236        http://kevan.org/brain.cgi?DDTNM
 "The truth will set you free, but first it will piss you off."




------------------------------

_______________________________________________
Xastir mailing list
Xastir at lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


End of Xastir Digest, Vol 60, Issue 8
*************************************

More information about the Xastir mailing list