[mythtv-users] segfaults at the end of mythfilldatabase

Tom Dexter digitalaudiorock at gmail.com
Mon Dec 10 22:05:40 UTC 2007


On 12/5 I upgraded my mythtv (fixes 0.20.2) from svn 14324 to 14814
under Gentoo.  I also upgraded from the 2.6.22 to the 2.6.23 kernel.

My daily mythfilldatabase runs appear to be completing
successfully...I have full listings and the status says it was
successfully.  However I get an odd segfault at the end of each run.
I just ran it at a command prompt to test it and I get the same thing.
 I get this output from mythfilldatabase at the end of the run:

2007-12-10 16:51:27.485 Connecting to backend server:
192.168.1.51:6543 (try 1 of 5)
2007-12-10 16:51:27.493 Using protocol version 31
2007-12-10 16:51:28.248 mythfilldatabase run complete.
2007-12-10 16:51:28.249 Received a remote 'Clear Cache' request
Segmentation fault

I also get the following in my messages log...here are examples of the
errors from several runs:

Dec  6 09:02:49 mythback kernel: mythfilldatabas[24794]: segfault at
bda93c9c eip 080cffca esp b597edac error 4
Dec  7 09:02:52 mythback kernel: mythfilldatabas[27082]: segfault at
bdabdf9c eip 080cffca esp b59eddac error 4
Dec  8 09:02:46 mythback kernel: mythfilldatabas[29341]: segfault at
f0800008 eip 080cffe9 esp b592fda4 error 6
Dec  9 09:02:49 mythback kernel: mythfilldatabas[31485]: segfault at
bda54324 eip 080cffca esp b5948dac error 6
Dec 10 09:02:52 mythback kernel: mythfilldatabas[1486]: segfault at
6ba37394 eip 080cffca esp b597ddac error 4

One difference I also see is that, in the mythfilldatabase logs, I
never used to get that line about receiving a remote 'Clear Cache'
request, but instead would get this:

2007-12-04 09:01:40.148 DataDirect: Deleting temporary files

Like I said, it doesn't appear to be causing any problems, but
segfaults are unnerving to say the least.  Anyone else ever get these?
 Thanks.

Tom


More information about the mythtv-users mailing list