Gary E. Miller <
address@hidden> ezt írta (időpont: 2020. ápr. 8., Sze, 19:47):
Very odd that your backtrace did not include the full backtrace.
Oh, you ran gdb aginst the core dump. That is your immediate
problem. Instead, start gdb, then have gdb load and run gpsmon.
I tried that, but unfortunately it didn't make much difference:
I started /usr/bin/gpsmon inside gdb, and let it run:
tc://localhost:2947 JSON slave driver>
(82) {"class":"VERSION","release":"3.20","rev":"3.20","proto_major":3,"proto_minor":14}
(256) {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttyAMA0","driver":"u-blox","subtype":"SW 7.03 (45969),HW 00040007","activated":"2020-04-09T10:42:35.236Z","flags":1,"native":1,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00,"mincycle":0.25}]}
(122) {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timing":false,"split24":false,"pps":true}
Program received signal SIGSEGV, Segmentation fault.
0x76e86094 in _nc_waddch_nosync () from /lib/libncurses.so.6
(gdb) thread apply all bt full
Thread 1 (Thread 0x76ff7820 (LWP 9930)):
#0 0x76e86094 in _nc_waddch_nosync () from /lib/libncurses.so.6
No symbol table info available.
#1 0x76e87234 in waddnstr () from /lib/libncurses.so.6
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
I googled for the error message, and based on the recommendations in
I even recompiled the gpsd package with -fno-omit-frame-pointer and -funwind-tables, but that sadly did not make any difference.
Luckily valgrind was more helpful as you can see from my other answer.
> > \"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
Well, I honestly have no idea. I gues cgps would be getting the same data, right? And it works without any problems.
Best Regards,
János
--
LinkedIn: linkedin.com/in/janosszigetvari__@__˚V˚
Make the switch to open (source) applications, protocols, formats now:
- windows -> Linux, iexplore -> Firefox, msoffice -> LibreOffice
- msn -> jabber protocol (Pidgin, Google Talk)
- mp3 -> ogg, wmv -> ogg, jpg -> png, doc/xls/ppt -> odt/ods/odp