[mythtv-users] MythArchive crash in RecordingSelector::updateRecordingList

Will Dormann wdormann at gmail.com
Sat Jun 21 14:41:28 UTC 2014


Hi folks,

I've recently disobeyed my mantra of "if it ain't broke, don't fix it"
and installed updates for mythtv.  First it was to run 0.27.1, and then
I was feeling lucky and updated to the latest available by mythbuntu:
fixes/0.27 [v0.27.1-16-gaa822f5] www.mythtv.org

I now notice that when I go to MythArchive, mythfrontend crashes after
selecting a recording to burn.  Specifically, after the dialog comes up
that states: "Retrieving File Information. Please Wait..."

When attached with a debugger, I see the following crash details:

-----

Program received signal SIGSEGV, Segmentation fault.
0x00007f8eccab0ce5 in RecordingSelector::updateRecordingList
(this=0x26076c0) at recordingselector.cpp:419
419	recordingselector.cpp: No such file or directory.



#0  0x00007f8eccab0ce5 in RecordingSelector::updateRecordingList
(this=0x26076c0) at recordingselector.cpp:419
        p = 0x7f8e28024cb0
        i = {_M_current = 0x7f8e2804fc60}
#1  0x00007f8eccab290c in RecordingSelector::setCategory
(this=0x26076c0, item=0x26087b0) at recordingselector.cpp:538
No locals.
#2  0x00007f8eccae94b0 in RecordingSelector::qt_static_metacall
(_o=0x26076c0, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0x7fff4c869870)
    at moc_recordingselector.cpp:69
        _t = 0x26076c0
#3  0x00007f8f94b6e87a in QMetaObject::activate(QObject*, QMetaObject
const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
No symbol table info available.
#4  0x00007f8f974f440c in MythUIButtonList::itemSelected
(this=0x465d310, _t1=0x26087b0) at moc_mythuibuttonlist.cpp:116
        _a = {0x0, 0x7fff4c869860}
#5  0x00007f8f9742a396 in MythUIButtonList::Select (this=0x465d310) at
mythuibuttonlist.cpp:120
        item = 0x26087b0

-----

I've tried with a different recording, and it crashes as well, so I
don't think that it's anything specific to any particular recording.
It's not clear if it was the switch from 0.27 to 0.27.1, or if it was
one of the incremental fixes provided in the mythbuntu repos.

Before I start playing "binary search" with restoring my backup
revisions, has anybody else seen this behavior, or have a guess as to
what may have caused it?


Thanks!
-WD


More information about the mythtv-users mailing list