Re: gpsmon segmentation fault

[Gary E. Miller]

Yo SZIGETVÁRI!

On Wed, 8 Apr 2020 11:04:36 +0200
SZIGETVÁRI János <address@hidden> wrote:


> Okay, I built a debug enabled package for gpsd, however it was of
> little use as according to the backtrace the crash happened in
> ncurses code, and I don't have any debug symbols for that:

We already knew the crash was in the ncurses code.  The thing to
discover is where in gpsmon code that call was made.

Very odd that your backtrace did not include the full backtrace.
 
> root@ntp:~# gdb --core core-gpsmon.26880.ntp.lan.1586331775

Oh, you ran gdb aginst the core dump.  That is your immediate
problem.  Instead, start gdb, then have gdb load and run gpsmon.


> As per the output, there is only one thread of gpsmon altogether, so
> at this point we don't have to worry how the separate threads
> interact.

gpsmon has two threads.  Just look at gpsmon.c

> > \"real_nsec\":999549916,\"clock_sec\":1586171794,\"clock_nsec\":135412671}\r\n\265b\1\0064\0\240\f\222\7\334!\371\3774\10\3\335\226\312\213\30\365N1\10\263*\302\33\306\3\0\0\0\0\0\0\0\0\0\0\4\0\0\0C\0\0\0\236\0\2\t\"g\1\0\r\302",
> > 18433) = 193
> >
> > What is that \302 ???
> >  
> 
> Maybe this:
> https://unicodelookup.com/#COMBINING/1

Yes, but in an incorrect location.  The only valid chars at the point
would be: {, \r, \n, or \0


RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

pgpsbTZs4oj2r.pgp
Description: OpenPGP digital signature