You need to enter "continue" in gdb after you attached it.


On 01/02/2011 08:46 PM, Karolis Narbutas wrote:

When debugger is attached to lirc PID, no other program can access it. Id i launch irw, it seems that irw hangs. No entries are entered in syslog. if i stop debugger and relaunch irw, it kills lirc process with the same error. Ithink lirc allows one interatcion with its process. Is there another way to debug it?

I also tried to compile lirc with debuging enabled and launch it with highiest debug level (-D5) but the output isthe same and no error information shown.


2010/12/30 Bob van Loosen <>
On 12/27/2010 06:15 PM, Karolis Narbutas wrote:
> Hi,
> I have installed lirc 0.8.7 pre3 and trying to use IR over portaudio.
> using this setup:
> My problem is this:
> when lirc starts at system startup, it segfaults when i try to access
> it with IRW or other program that i configured to use lirc, i.e. XBMC.
Can you attach gdb with "sudo gdb -p `pidof lircd`", enter "set logging
on" in gdb, make lircd crash, then enter "thread apply all bt" in gdb.
Then you have a gdb.txt file sitting in the working directory with a
backtrace in it, can you post that file here?


Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption