Opened 11 years ago

Closed 11 years ago

#5532 closed defect (fixed)

MBE firewire records fine, attempt to start recording from SBE firewire causes immediate segfault

Reported by: robert.mcnamara@… Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no

Description

This behavior is reproducible 100% of the time w/ SVN trunk revision 17747.

My set up contains a firewire STB on the Master Backend, as well as one on the Slave Backend. A firewire recording on the Master backend will work fine. Attempt to start a second recording simultaneously, however, will cause the MBE to segfault (The SBE does *not* crash).

Included are a backtrace (gdb.txt) and the output of mythbackend -v all (crash.log), both from the MBE.

Attachments (4)

gdb.txt (42.1 KB) - added by robert.mcnamara@… 11 years ago.
gdb backtrace
crash.log (18.7 KB) - added by robert.mcnamara@… 11 years ago.
mythbackend -v all, only the tail to fit size limit.
autoexpire-bandaid.patch (5.0 KB) - added by jppoet@… 11 years ago.
shot in the dark - possible band-aid for this crash
SBE-Crash.txt (20.3 KB) - added by robert.mcnamara@… 11 years ago.
tail of SBE at time of MBE crash with -v all,

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by robert.mcnamara@…

Attachment: gdb.txt added

gdb backtrace

Changed 11 years ago by robert.mcnamara@…

Attachment: crash.log added

mythbackend -v all, only the tail to fit size limit.

Changed 11 years ago by jppoet@…

Attachment: autoexpire-bandaid.patch added

shot in the dark - possible band-aid for this crash

comment:1 Changed 11 years ago by robert.mcnamara@…

Regrettably the patch doesn't seem to have any effect. I am attaching a -v all log from the slave backend just so there is some sense of what it is trying to do when the MBE Segfaults.

Changed 11 years ago by robert.mcnamara@…

Attachment: SBE-Crash.txt added

tail of SBE at time of MBE crash with -v all,

comment:2 Changed 11 years ago by cpinkham

Resolution: fixed
Status: newclosed

Issue reported as no longer occurring after [17864], so maybe that fixed this issue as well.

Note: See TracTickets for help on using tickets.