[Xastir] Fwd: Canadian Call Sign lookup on Xastir-Ubuntu 10.04 Live CD

[Jeremy Utley]

On Sun, Jul 18, 2010 at 9:39 PM, David Flood <davidf4 at mindspring.com> wrote:
> Lee,  I see references to curl...I wonder if this is the same long
> URL/broken curl issue that showed up when OSM was being debugged.
>
> Any chance you can do a compile --without-libcurl and see if the same error
> occurs?
>
> Dave
> KD7MYC

I don't think curl is the problem.  That's showing up in the memory
map part of the output, meaning the curl library is loaded into
memory, which you would expect.  The backtrace:

======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x50)[0xfa3390]
/lib/tls/i686/cmov/libc.so.6(+0xe12ca)[0xfa22ca]
/lib/tls/i686/cmov/libc.so.6(__fgets_chk+0x129)[0xfa25e9]
xastir[0x8153328]
xastir[0x80bfddd]
/usr/lib/libXt.so.6(XtCallCallbackList+0xb1)[0xbee4e1]
/usr/lib/libXm.so.2(+0xa56d6)[0x5e76d6]
/usr/lib/libXm.so.2(+0xa5eb7)[0x5e7eb7]
/usr/lib/libXm.so.2(_XmDispatchGadgetInput+0x182)[0x5bf5c2]
/usr/lib/libXm.so.2(_XmGadgetActivate+0x3e)[0x5d90ce]
/usr/lib/libXt.so.6(+0x454cb)[0xc264cb]
/usr/lib/libXt.so.6(_XtTranslateEvent+0x394)[0xc26cc4]
/usr/lib/libXt.so.6(XtDispatchEventToWidget+0x46a)[0xbfcd2a]
/usr/lib/libXt.so.6(+0x1c56b)[0xbfd56b]
/usr/lib/libXt.so.6(XtDispatchEvent+0xad)[0xbfc3fd]
/usr/lib/libXt.so.6(XtAppMainLoop+0x54)[0xbfc5c4]
xastir[0x8104717]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xed7bd6]
xastir[0x804f231]

leads me to believe the problem is actually something in Xastir or the
Motif libraries trigger up in the glibc code - most likely having to
do with buffer overflow fortification.  Unfortunately, since all the
system libraries have no debug symbols in them, it's probably going to
be hard to trace out where in the code the problem is.  Curt might be
able to make more sense of this than I can, and my limited knowledge
of C debugging doesn't give me any other ideas of where to look.
Looks like even the Xastir binary has been stripped of debugging
symbols - Curt - does Xastir's make install strip the binary by
default?  If there's a flag to disable the stripping of the binary,
you MIGHT be able to turn that off, and get some info of where in the
code the buffer overflow occurs.

Jeremy