Opened 12 years ago

Closed 12 years ago

#3530 closed defect (invalid)

mythbackend crashes with a segfault in locking code

Reported by: anonymous Owned by: Isaac Richards
Priority: major Milestone: 0.21
Component: mythtv Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no


I am experiencing mythbackend crashes on daily basis with latest myth rpms from ATRPMs bleeding (mythtv-suite-0.21-159_trunk_r13460.fc6). I have been able to get a core file and the backtrace is below:

Core was generated by `/usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pidfi'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000003b55ffdcd4 in QMutex::lock () from /usr/lib64/qt-3.3/lib/
(gdb) bt
#0 0x0000003b55ffdcd4 in QMutex::lock () from /usr/lib64/qt-3.3/lib/
#1 0x00000034bfc30f5e in MythSocket::UpRef? () from /usr/lib64/
#2 0x0000000000468ca9 in QMap<QString, QString>::end ()
#3 0x0000003b55d60456 in QObject::event () from /usr/lib64/qt-3.3/lib/
#4 0x0000003b55d00105 in QApplication::internalNotify () from /usr/lib64/qt-3.3/lib/
#5 0x0000003b55d015c4 in QApplication::notify () from /usr/lib64/qt-3.3/lib/
#6 0x0000003b55d010f9 in QApplication::sendPostedEvents () from /usr/lib64/qt-3.3/lib/
#7 0x0000003b55caeddc in QEventLoop::processEvents () from /usr/lib64/qt-3.3/lib/
#8 0x0000003b55d178c1 in QEventLoop::enterLoop () from /usr/lib64/qt-3.3/lib/
#9 0x0000003b55d17792 in QEventLoop::exec () from /usr/lib64/qt-3.3/lib/
#10 0x0000000000448041 in HttpServerExtension::HttpServerExtension?$base ()
#11 0x0000003b4f61da44 in libc_start_main () from /lib64/
#12 0x000000000041ab79 in QGList::~QGList$delete ()
#13 0x00007fffc5d5ba18 in ?? ()
#14 0x0000000000000000 in ?? ()

Unfortunately, 'bt full' does not contain any more information but if needed, I can attach the core file (it's about 270MB)

Change History (2)

comment:1 Changed 12 years ago by anonymous

I missed adding some detail! I appologize for that!

I am running on FC6 x86_64, kernel 2.6.20-1.2948.fc6, glibc-2.5-10.fc6

comment:2 Changed 12 years ago by stuartm

Resolution: invalid
Status: newclosed

We need a backtrace with a debug build, according to the instructions here:

The supplied backtrace is missing essential information. I also suspect that this crash may be a result of a bad build. If I'm right then the crash will disappear when you build it yourself and if not then at least we will get a decent backtrace to help fix it.

Note: See TracTickets for help on using tickets.