On Tue, 2009-03-10 at 00:13 +0100, Georg Martius wrote: > Hi, Hi,
> maybe it was mentioned before but I could not find it. > How to debug transcode with gdb? With me it stops immediately with > [1] Stopped gdb ~/bin/transcode > and if I resume it with "fg" I get > [New Thread 0xb7b028c0 (LWP 30131)] > > Program received signal SIGTTOU, Stopped (tty output). > [Switching to Thread 0xb7b028c0 (LWP 30131)] > 0xb7f20410 in __kernel_vsyscall () Hi, I don't usually go step-by-step when debugging: I do just use tc_log*()[1]. Yes, this is spartan, but in my experience it's enough in fair amount of cases. I use gdb mostly to analyze transcode post-mortem by inspecting the coredumps. +++ [1] maybe someday I'll eventually learn to deal with gdb, or I'll just find a good frontend. -- Francesco Romani // Ikitt http://fromani.exit1.org ::: transcode homepage http://tcforge.berlios.de ::: transcode experimental forge
