Re: [Jack-Devel] debug netjack/jacktrip to understand the code

PrevNext  Index
DateMon, 24 Sep 2012 08:55:06 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToLeonardo Gabrielli <[hidden] at univpm dot it>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToLeonardo Gabrielli [Jack-Devel] debug netjack/jacktrip to understand the code
Follow-UpLeonardo Gabrielli Re: [Jack-Devel] debug netjack/jacktrip to understand the code
On Mon, Sep 24, 2012 at 5:31 AM, Leonardo Gabrielli
<[hidden]>wrote:

>  Hello list,
> I want to learn more about how netjack and jacktrip work. Instead of
> simply looking at the code, I would like to run them in debug mode, i.e.
> putting breakpoints, reading variables and so on. I'm a bit rusty on
> debugging under linux with gdb, would somebody like to help me figure out
> how to do that?
> A draft of the steps:
> 1. compile jacktrip with debug symbols (probably by adding -g to the
> arguments of g++ in the makefile?)
> 2. type in terminal: gdb jacktrip
> 3. setting breakpoints
> 4. type the gdb command: run
>


using gdb for realtime code is generally not a very good way to analyse
them. the moment you hit a breakpoint, you will likely stop the entire jack
"system" from working until you quit and restart jack again. its much
better to use printf/cerr statements to print out information that is of
interest to you (and generally redirect that output to a file).
PrevNext  Index

1348491746.8464_0.ltw:2,a <CAFa_cK=WAU6v9-ux_Ujia9fzN0O-3FZkTBTDPwmjqDt5y1eXWw at mail dot gmail dot com>