[mythtv] Segfault in frontend in mpeg decoder (backtrace attached)
Ed Wildgoose
edward.wildgoose at frmhedge.com
Sat Dec 27 15:06:41 EST 2003
Ed Wildgoose wrote:
> Hi, seems like there is a lot to record on tv at the moment. Must be
> a holiday or something....
>
> I have one file which may have a glitched frame in it. It causes a
> crash in the mpeg decoder on latest CVS. Could someone please take a
> look at the backtrace for me? (Is this related to the viaslice
> thread?) The source of the mpeg stream was a DVB card.
>
Hmm, are no other DVB users seeing this? It's quite annoying because it
is killing the backend regularly as well (I assume it's as a result of
the commercial tagging?). Backend bt is not very helpful though:
[mpeg2video @ 0x8502228]Warning MVs not available
[mpeg2video @ 0x8502228]00 motion_type at 33 0
[mpeg2video @ 0x8502228]ac-tex damaged at 43 8
[mpeg2video @ 0x8502228]00 motion_type at 11 9
[mpeg2video @ 0x8502228]00 motion_type at 1 13
[mpeg2video @ 0x8502228]concealing errors
[mpeg2video @ 0x8502228]Warning MVs not available
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 606222 (LWP 3836)]
0x082904e4 in mpeg_decode_slice (avctx=0x8502228, pict=0x45e0481c,
start_code=14, buf=0x45e04734, buf_size=0) at mpeg12.c:2226
2226 mpeg12.c: No such file or directory.
in mpeg12.c
Current language: auto; currently c
(gdb)
Continuing.
Cannot find user-level thread for LWP 3836: generic error
(gdb)
Continuing.
Cannot find thread 606222: generic error
(gdb) thread apply all bt full
Cannot find new threads: generic error
(gdb)
More information about the mythtv-dev
mailing list