[mythtv] mythbackend segemenation fault on scheduling items

[Michael T. Dean]

On 10/02/2007 05:26 PM, Ma Begaj wrote:
> I am receiving segementation fault errors with mythbackend and
> mythbackend crashes:
> the last line in the log file is always the same ... as you can see in
> these three logfiles. I made while loop which restarts mythbackend
> after  few seconds with a new log file:
>
> mythtv at mythbox:/tmp$ tail -n 5 mythback2007-10-02T2*
> ==> mythback2007-10-02T20:24:13 <==
> 2007-10-02 23:00:57.034 MainServer::HandleAnnounce Monitor
> 2007-10-02 23:00:57.034 adding: mythbox as a client (events: 1)
> 2007-10-02 23:00:57.035 GetRecordBasename found no entry
> 2007-10-02 23:00:57.083 GetRecordBasename found no entry
> 2007-10-02 23:00:57.130 Scheduled 28 items in 0.2 = 0.00 match + 0.16 place
>
> ==> mythback2007-10-02T23:01:06 <==
> 2007-10-02 23:13:59.131 MainServer::HandleAnnounce Monitor
> 2007-10-02 23:13:59.131 adding: mythbox as a client (events: 1)
> 2007-10-02 23:13:59.132 GetRecordBasename found no entry
> 2007-10-02 23:13:59.139 GetRecordBasename found no entry
> 2007-10-02 23:13:59.266 Scheduled 26 items in 0.2 = 0.00 match + 0.15 place
>
> ==> mythback2007-10-02T23:14:13 <==
> 2007-10-02 23:15:58.496 MainServer::HandleAnnounce Monitor
> 2007-10-02 23:15:58.496 adding: mythbox as a client (events: 1)
> 2007-10-02 23:15:58.496 GetRecordBasename found no entry
> 2007-10-02 23:15:58.501 GetRecordBasename found no entry
> 2007-10-02 23:15:58.646 Scheduled 28 items in 0.2 = 0.00 match + 0.16 place
>
> These are the last 5 lines of log files. The last line is always
> "Scheduled ... items..."
>
> Could QT be the reason? Somebody from the list told me that QT <3.3.8
> causes segmentation fault with mythfilldatabase.
>
> I am using QT 3.3.8. If I upgrade QT, do I have to recompile mythtv?

QT = 3.3.8 causes seg faults at application shutdown.  If using QT <
3.3.8, everything works.

However, a mythfilldatabase crash at shutdown should not crash
mythbackend.  I'm thinking the "GetRecordBasename found no entry" is the
culprit (and is likely due to using differing versions of mythtv
programs (i.e. mythbackend and mythfrontend are different versions) or
due to a corrupt database--i.e. from a failed DB schema upgrade, which
itself was likely due to bad data in the database).

Really this is a question for the -users list.  If you were proposing a
patch to change mythtv, it would be appropriate for the -dev list. 
Troubleshooting issues should /always/ start on the -users list.

Mike