[mythtv-users] Ticket #9704 Hang/Deadlock locked

[John Drescher]

On Sun, Feb 5, 2012 at 9:38 PM, John Drescher <drescherjm at gmail.com> wrote:
>>> 1. How do I debug this so that someone possibly can give me advice?
>>
>> Debugging is documented at:
>>   http://www.mythtv.org/wiki/Debugging
>>
>> If you are not familiar with the tools (as you suggest later in
>> your post), and the description in the above is not adequate,
>> help yourself now, and others in the future, by pointing out
>> what is not clear in the wiki (personally, having used all the
>> tools, it is clear to me, but I understand that what is obvious
>> to someone with experience in the field may not be clear to
>> others).
>>
>
> This has helped. Although there was a sticking point. It does not seem
> that there is a way to enable debugging symbols in gentoo in either of
> the overlays I used. The first was the mt-mythtv which I have used for
> years but during the process I moved to the ebuilds in the
> MythTv/packaging on github
>
> https://github.com/MythTV/packaging
>
> and although the instructions in the wiki
>
> http://www.mythtv.org/wiki/Debugging#Gentoo_ebuilds
>
> did not enable debugging symbols but it seems to have fixed the issue.
> I will probably ask about that in a different thread.
>
> Instead of a 50% chance of a recording causing mythbackend to deadlock
> and no longer accept any connections. I have not been able to produce
> this once in about 5 to 10 programs recorded. I have not tried the
> frontend yet however. I have also used mythweb pretty heavily after
> starting a program and that also caused a deadlock.
>
Not solved but more interesting. Running the fontend it was very easy
to get the backend to deadlock. Just go to livetv and change the
channel a few times by typing the next channel number. That was when
running mythbackend from the init scripts. When run in gdb as root
mythbackend was much harder to deadlock but it still happened although
I did not get anything useful from that.

Since its 12:38 am I have to give this up for now. I am leaving
mythbackend running as root inside gdb since that seems to work much
better that way.

John