No subject

mythcommflag[23144]: segfault at 10 ip 00007f7f2135fdc5 sp 00007f7f10dd1f78 
error 4 in libmythdb-0.23.1.so.0.23.1[7f7f21310000+9b000]

What I dont understand is why the jobqueue shows that mythcommflag completed 
successful with ZERO breaks, but the QUERY_COMMBREAK shows breaks.

I had one recording tonight and the above message in syslog, so I sure that 
mythcommflag had the segfault with flagging the one show being recorded.

The DB jobqueue table shows 0 commercual breaks, with a status of 272 
(success).  Mythweb shows the same information.


691 4251 2010-10-15 21:00:00 2010-10-15 21:00:03 2 0 2 272 2010-10-15 21:00:03 
myth [BLOB - 0B] 0 commercial break(s) 2010-10-15 21:00:03 


Looking at the backend log file I see these messages:
2010-10-15 22:00:08.134 CommDetect::GetCommBreakMap()
2010-10-15 22:00:08.148 CommDetect::CleanupFrameInfo()
2010-10-15 22:00:08.575 CommDetect::BuildAllMethodsCommList()
2010-10-15 22:00:09.595 Final Commercial Break Map
2010-10-15 22:00:13.972 commflag: Commercial Flagging Finished: The Good Guys 
"Dan on the Run" recorded from channel 4251 at Fri Oct 15 21:00:00 2010 (0 
commercial break(s))

Which also shows ZERO breaks...

If I send a QUERY message to the backend, the response I receive shows 12 
breaks.

2010-10-15 23:01:59.950 MythSocket(7f7cac05ebc0:8): read  <-  8 31      
QUERY_COMMBREAK 4251 1287190800
2010-10-15 23:01:59.951 ProgramInfo(): Updated pathname '':'' -> 
'4251_20101015210000.mpg'
2010-10-15 23:01:59.975 MythSocket(7f7cac05ebc0:8): write ->  8 266     
12[]:[]4[]:[]0[]:[]0[]:[]5[]:[]0[]:[]527[]:[]4[]:[]0[]:[]23143[]:...

Which one is correct, the jobqueue or the QUERY_COMMBREAK command?

Thanks, Mike