Another annoying dvd playback bug
I guess it might be related to the bug labeled "Threading issue" here
this concerns (g)mplayer. I seem to be getting this error _very_ often
when trying to play dvds:
MPlayer interrupted by signal 11 in module: decode_video
- MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in
- MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We
won't help unless you provide this information when reporting a
I should mention that while gmplayer is spitting various errors at me
the CPU usage of gmplayer is nearly 100% thus similar symptoms as
xine/gxine/growisofs, but maybe not the same problem. I recompiled
gmplayer with --enable-debug but no idea what to do now, i never used gdb.
This is getting very frustrating because gmplayer, xine, gxine dont work
as they should, i cant watch my dvds. Beep-media-player which i use for
audio playback doesnt work well either (100% usage on exiting the
program, while the process itself doesnt exit and has to be killed
manually with -9)
I really want my desktop to be somewhat "usable".
#1 Updated by wa1ter almost 9 years ago
Petr Janda wrote:
> ...I recompiled
> gmplayer with --enable-debug but no idea what to do now, i never used gdb...
Does plain mplayer work any better than gmplayer?
Anyway, to run an app in gdb, just type 'gdb gmplayer' from a
shell prompt, and then type 'run' at the gdb prompt.
If you normally start gmplayer with an argument, like the name
of a file, then type 'run path-to-file' instead.
When the app crashes it won't disappear from the screen as it
usually would, it will just freeze. That's when you go back
to the gdb prompt and type 'bt' (backtrace).
Hm. I've never done a gdb 'disassembly' so I'd better find out
what it means.
#3 Updated by erik-wikstrom almost 9 years ago
On 2006-07-30 23:44, firstname.lastname@example.org wrote:
>>MPlayer interrupted by signal 11 in module: decode_video
>>- MPlayer crashed by bad usage of CPU/FPU/RAM.
> Please, have a look on google with "signal 11".
Signal 11 is segmentation violation (or segmentation fault/segfault) and
is the "standard" error when something is not right. It's caused by the
app trying to access unallocated memory and is often caused by some
stray pointer, however the cause can be anything from buggy code to bad
compiler optimizations or faulty hardware.
As for the requested disassembly they probably mean a disassembly of the
function that caused gmplayer to crash. Get the backtrace as Walt said
then for the function at the top run "disassemble func" where func is
the name of the topmost function in the backtrace.
#4 Updated by corecode over 8 years ago
Petr Janda wrote:
> I guess it might be related to the bug labeled "Threading issue" here
> http://leaf.dragonflybsd.org/mailarchive/bugs/2006-07/msg00151.html. But
> this concerns (g)mplayer. I seem to be getting this error _very_ often
> when trying to play dvds:
is this still current?