Opened 16 years ago
Closed 16 years ago
#5532 closed defect (fixed)
MBE firewire records fine, attempt to start recording from SBE firewire causes immediate segfault
| Reported by: | 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)
Change History (6)
Changed 16 years ago by
mythbackend -v all, only the tail to fit size limit.
Changed 16 years ago by
| Attachment: | autoexpire-bandaid.patch added |
|---|
shot in the dark - possible band-aid for this crash
comment:1 Changed 16 years ago by
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 16 years ago by
| Attachment: | SBE-Crash.txt added |
|---|
tail of SBE at time of MBE crash with -v all,
gdb backtrace