[Xastir] Maybe a clue to the MaxConcern messup...

[Richard Polivka, N6NKO]

I managed to catch a bad message today. Luckily, I was saving ALL info 
from xastir. I put the net.log file into khexedit and picked out the 
following line. Here it is in hex:

4b 45 59 53 4d 57 3e 41 50 52 53 2c 71 41 4f 2c
57 58 53 56 52 3a 3b 4b 45 59 4d 31 37 33 30 7a
2a 30 37 31 38 33 30 7a 32 33 34 32 2e 36 30 4e
4d 30 37 30 34 33 2e 32 30 57 57 43 65 6e 74 65
72 20 6f 66 20 4d 61 78 43 6f 6e 63 65 72 6e 20
7d 64 30 62 53 92 54 91 54 90 53 8e 52 9f 29 c1
53 8f 7b 37 48 55 41 49 0a

db.c is choking on line 6, starting at character 5 which is a "C". The 
decoded position numbers are too big for the conditionals to accept. So, 
it spits out the warning message.

So it looks like either WXSVR is choking on the data from the NWS or is 
taking a flight of fancy on the incoming data.

Good luck with the search.

73 from 807,

Richard, N6NKO