gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gpsmon segmentation fault


From: SZIGETVÁRI János
Subject: Re: gpsmon segmentation fault
Date: Thu, 9 Apr 2020 12:54:26 +0200

Hi Paul,

Paul Fertser <address@hidden> ezt írta (időpont: 2020. ápr. 8., Sze, 19:53):
Hey Gary, SZIGETVÁRI,

And if that doesn't help you might have luck running the same under
"valgrind" (just valgrind gpsmon ..., no tricky options needed), it
often gives more useful backtraces as the problems are detected
earlier.

Unfortunately valgrind can't be installed from an OS package, so I compiled it myself.
Luckily it produced pretty useful output:

root@ntp:~# valgrind /usr/bin/gpsmon
==9937== Memcheck, a memory error detector
==9937== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==9937== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==9937== Command: /usr/bin/gpsmon
==9937==
ESC[?1049hESC[22;0;0tESC[1;24rESC(BESC[mESC[4lESC[?7hESC[?1hESC===9937== Invalid write of size 4
==9937==    at 0x145D4: refresh_statwin (gpsmon.c:442)
==9937==    by 0x149E7: curses_init (gpsmon.c:490)
==9937==    by 0x176D7: main (gpsmon.c:1379)
==9937==  Address 0x4bcfaf0 is 24 bytes before a block of size 16 in arena "client"
==9937==

valgrind: m_mallocfree.c:280 (mk_plain_bszB): Assertion 'bszB != 0' failed.
valgrind: This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata.  If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away.  Please try that before reporting this as a bug.

host stacktrace:
==9937==    at 0x58040C94: ??? (in /usr/lib/valgrind/memcheck-arm-linux)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 9937)
==9937==    at 0x1465C: refresh_statwin (gpsmon.c:444)
==9937==    by 0x149E7: curses_init (gpsmon.c:490)
==9937==    by 0x176D7: main (gpsmon.c:1379)
client stack range: [0x7DA42000 0x7DA5CFFF] client SP: 0x7DA5BE68
valgrind stack range: [0x41FDC000 0x420DBFFF] top usage: 25116 of 1048576

Thaks for the idea!

Best Regards,
János
--
Janos SZIGETVARI
RHCE, License no. 150-053-692

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
 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]