[mythtv] Fwd: Mythbackend quietly exits when recording channel Five (uk-Crystal Palace)

[scratch1701]

Hello everyone,

Just a quick update: I now highly suspect that the reason for these
segmentation faults is using the EIT programme guide. Based on a
problem on another thread, I decided to switch to using xmltv to
download the program guides, and I seem to be able to record as per
normal.

I do have "ac-tex damaged" errors all over the logs, but it seems to
have done the trick. I'll keep testing.

Cheers,
/ken

On 1/22/07, scratch1701 <scratchbuild at gmail.com> wrote:
> hello All,
>
> I applied the patch, and recompiled MythTV0.20 as per your
> instructions. Then I ran mythbackend with gdb. After that, I turned on
> mythfrontend, and set a recording (on channel Five). Then exited
> mythfrontend.
>
> Normally, it takes about 10 minutes, and Mythbackend will quit. The
> standard output usually looks like this:
>
> ---
> 2007-01-22 21:02:50.017 Expiring Unknown from Mon Jan 22 20:59:39
> 2007, 0 MBytes, forced expire (LiveTV recording)
> 2007-01-22 21:02:50.020 Expiring Unknown from Mon Jan 22 20:59:41
> 2007, 19 MBytes, forced expire (LiveTV recording)
> 2007-01-22 21:02:53.861 MainServer::HandleAnnounce Playback
> 2007-01-22 21:02:53.861 adding: foofaraw as a client (events: 0)
> 2007-01-22 21:18:36.169 EITScanner: Added 5252 EIT Events
> 2007-01-22 21:18:36.170 Reschedule requested for id -1.
> 2007-01-22 21:18:36.191 Scheduled 1 items in 0.0 = 0.01 match + 0.01 place
> Segmentation fault
> ---
>
> After 15 minutes, I restarted Mythfrontend, and it could not connect
> to mythbackend. I believe this is when mythbackend quit. However, gdb
> says that the application is still running. I hit Ctrl-C, and got the
> gdb.txt file which I have attached here. I don't see any segfaults in
> the file, so I hope it does show something...
>
> Cheers.
> /ken
>
> > I mean run without -v record,channel,siparser.
> > As Janne mentioned, try running with the patch
> > and let us know how it goes...
>
>
>