[mythtv] crash in mythbackend

Chris Pinkham cpinkham at bc2va.org
Mon May 12 02:21:50 EDT 2003

If you want me to fix it, I can take a look at it Monday night.  If the
flagging thread has its own db connection does it even need to
worry about locking?  Better safe than sorry I guess.

> On Sunday 11 May 2003 11:50 pm, Craig Longman wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 311316 (LWP 4550)]
> > 0x40981efa in mallopt () from /lib/libc.so.6
> This here's what I needed -- just couldn't tell which thread actually crashed, 
> otherwise.  Looks like the commercial finding thread needs to get its own db 
> connection, and just from looking things over, looks like some of the other 
> db stuff the commercial finding code is doing isn't locking properly, either.  
> I'll get it fixed tomorrow sometime.
> Isaac


More information about the mythtv-dev mailing list