Opened 16 years ago
Closed 16 years ago
#5114 closed defect (fixed)
ASSERT failure in QList<T>::operator[]: "index out of range"
Reported by: | Owned by: | Isaac Richards | |
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | mythtv | Version: | head |
Severity: | low | Keywords: | ASSERT |
Cc: | Ticket locked: | no |
Description
not shure what caused this one i left the room and returned to an error in gdb
MythTV Version : 16870M MythTV Branch : trunk
(gdb) bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb55a3875 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xb55a5201 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xb582101d in qt_message_output () from /usr/lib/libQtCore.so.4 #4 0xb58210a1 in qFatal () from /usr/lib/libQtCore.so.4 #5 0xb58210f8 in qt_assert_x () from /usr/lib/libQtCore.so.4 #6 0x0808295c in QList<QString>::operator[] (this=0xbfb45390, i=3) at /usr/include/qt4/QtCore/qlist.h:394 #7 0xb7984120 in TV::customEvent (this=0x9d41c20, e=0x837e408) at tv_play.cpp:6518 #8 0xb58f1c16 in QObject::event () from /usr/lib/libQtCore.so.4 #9 0xb5b2a44d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #10 0xb5b2a74e in QApplication::notify () from /usr/lib/libQtGui.so.4 #11 0xb58df456 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #12 0xb58e281f in ?? () from /usr/lib/libQtCore.so.4 #13 0xbfb47bec in ?? () #14 0x09d41c20 in ?? () #15 0x0837e408 in ?? () #16 0xb58253d7 in ?? () from /usr/lib/libQtCore.so.4 #17 0x081bb9b4 in ?? () #18 0xb5964e20 in ?? () from /usr/lib/libQtCore.so.4 #19 0xbfb45a48 in ?? () #20 0xb58df92d in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 Backtrace stopped: frame did not save the PC
Attachments (1)
Change History (3)
comment:1 Changed 16 years ago by
Changed 16 years ago by
Attachment: | 5114_patch.patch added |
---|
Note: See
TracTickets for help on using
tickets.
looks like the flagger is sending a commflag_update without a flag map
so the [3] refers to a field which doesnt exist causing an abort
i suspect that i can just .count() the qlist and ignore the update if its empty, but it may actualy be a bug in the flagger which shouldnt send out empty updates