[mythtv] mythbackend crashes with segmentation fault after the specific sequences of events.

Mudit Wahal mwahal at gmail.com
Fri Jun 17 03:09:25 UTC 2005


Thanks. I'll take a look at the script and make sure that there should
be only one socket connection in it and not multiple. I picked up this
python script from a website and fixing it as per the frontend logs
I've captured.

I'm running this script in a loop with a 3 second sleep. Is it
possible that the prior connections are still open and not closed in
last 3 seconds ?

while (1)
    sleep 3

I'll let you know my findings.


On 6/16/05, Isaac Richards <ijr at case.edu> wrote:
> On Thursday 16 June 2005 09:04 pm, Mudit Wahal wrote:
> > Isaac,
> >
> > My script is based on debug output logged from the mythfrontend. I'm
> > modeling my script based on how the frontend is sending commands when
> > it switches to liveTV to when I stop watching live TV.
> You're missing the fact that the frontend is opening multiple connections with
> your logging.  There's 3 separate sockets in there, not 1.  This is also the
> cause of your newest crash - you're sending different things on different
> connections than what the frontend would, and the backend is assuming that it
> gets mostly proper input.
> Isaac
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

More information about the mythtv-dev mailing list