[mythtv] [mythtv-commits] Ticket #6725: segmentation fault in mythbackend

[Michael T. Dean]

On 07/16/2009 09:23 AM, Simon Kenyon wrote:
> Nick Morrott wrote:
>> On 16/07/2009, Simon Kenyon wrote: 
>>> MythTV wrote:  
>>>> #6725: segmentation fault in mythbackend
...
>>>> Changes (by stuarta):
>>>>
>>>>  * status:  new => infoneeded_new 
>>>  what more information do you need?
>>>  i'm a little confused
>>>  not sure if you need additional information from me
>>>
>>>  the backend has a PVR-350 connected to a STB using RGB
>>>  it has two DVB-S cards, a Nexus-S and and a budget 1500
>>>  it is hard to tell remotely, but i think i am using the 1500
>>>  i only have one DVB card configured in at the moment
>>>     
...
>> Echoing Mike Dean's frequent suggestion, I would do a "Delete all
>> capture cards" and then just configure the card you are using for
>> testing. Your log indicated you are using the DVB-S card that uses the
>> "ST STV0299 DVB-S" frontend (DVB adapter 1).   
> but as you know yourself, deleting all capture cards and adding them 
> again is a bit drastic
> this is a production system - i'm not using it for "testing" - i'm 
> using it for "watching" :-)
...
> it seems that if you get the channel list out of sync with what is 
> being broadcast, then the backend becomes unstable
> as you know yourself, the channels that are broadcast on Astra 28.2E 
> change on an almost daily basis
>
> anyway. i will do as you say
> pity. i had more or less got my channel list sorted out

If you're that concerned about it, give me a week or two and I'll have a 
patch for the restore script that--given a full backup--will fix 
channels for you (set the user-modifiable things back to the way they were).

Oh, and I think the only reason that it was still marked as 
infoneeded_new was because they hadn't gotten around to changing it back 
after realizing you had good backtraces on there.

Mike