RE: Using gpsd-dbg

[Jared Hagel]

Thanks Gary. I am building from source. Turning on debugging before building 
sounds like the better option to me. I'll do that - after I figure out how 😊. 
I'm sure it won't be hard to find. 

-----Original Message-----
From: gpsd-dev <gpsd-dev-bounces+jared.hagel=vontas.com@nongnu.org> On Behalf 
Of Gary E. Miller
Sent: Tuesday, September 14, 2021 12:03 PM
To: gpsd-dev@nongnu.org
Subject: Re: Using gpsd-dbg

Yo Jared!

On Tue, 14 Sep 2021 15:45:44 +0000
Jared Hagel <jared.hagel@vontas.com> wrote:

> Hello everyone,
> 
> From https://gpsd.gitlab.io/gpsd/troubleshooting.html I see "In case 
> you need to debug the gpsd or its clients using gdb or the python 
> debugger the gpsd-dbg package is provided. It should contain all 
> necessary debug symbols to create useful backtraces."
> 
> Can someone explain how I use gpsd-dbg in combination with gdb to 
> debug gpsd? I find this more efficient sometimes than adding a whole 
> bunch of printf statements. I can't seem to find an exaplanation 
> elsewhere on how to do this...


The gpsd project release no package named gpsd-dbg.  In fact, gpsd release no 
packages at all.  Only tar balls.

I suspect you are reading the section on Ubuntu/Debian.  That package comes 
from them, not us.

If you build from source, then just turn on debugging before building.
After that gdb works as expected.

Maybe some Ubuntu person here knows how to use it.

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

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