[csw-users] MPlayer - Testing and Unstable

Uwe Dippel udippel at gmail.com
Tue Oct 16 12:49:42 CEST 2007


I downloaded MPlayer from unstable, updated 22-09, and found some
problems (see below).
The MPlayer mailing list gave some advice and suggested to use a
recent version "Please test latest svn (or, at least, rc2)".
I found a very fresh one in Testing of yesterday that doesn't expose
the iconv-problem. Still it is
MPlayer 1.0rc1-4.0.2 (C) 2000-2006 MPlayer Team

Any good reason not to use a more recent version ?

Thanks,

Uwe


$ mplayer vcd:// -cdrom-device /dev/rdsk/c1t1d0s2
iconv: conversion from UTF-8 to 646 unsupported
MPlayer 1.0rc1-3.4.5 (C) 2000-2006 MPlayer Team
iconv: conversion from UTF-8 to 646 unsupported
CPU: AMD Sempron(tm) Processor 2600+ iconv: conversion from UTF-8 to
646 unsupported
(Family: 15, Model: 44, Stepping: 2)
iconv: conversion from UTF-8 to 646 unsupported
3DNow supported but disabled
iconv: conversion from UTF-8 to 646 unsupported
3DNowExt supported but disabled
iconv: conversion from UTF-8 to 646 unsupported
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 0 SSE2: 0
iconv: conversion from UTF-8 to 646 unsupported
Compiled for x86 CPU with extensions:iconv: conversion from UTF-8 to
646 unsupported
 MMXiconv: conversion from UTF-8 to 646 unsupported
 MMX2iconv: conversion from UTF-8 to 646 unsupported

iconv: conversion from UTF-8 to 646 unsupported

Playing vcd://.
iconv: conversion from UTF-8 to 646 unsupported
track 01:  adr=1  ctrl=4  format=2  00:02:00  mode: 2
iconv: conversion from UTF-8 to 646 unsupported
track 02:  adr=1  ctrl=4  format=2  00:38:02  mode: 2
iconv: conversion from UTF-8 to 646 unsupported


MPlayer interrupted by signal 11 in module: demux_open
iconv: conversion from UTF-8 to 646 unsupported
- MPlayer crashed by bad usage of CPU/FPU/RAM.
 Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
 disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
iconv: conversion from UTF-8 to 646 unsupported
- 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 can't and
 won't help unless you provide this information when reporting a possible bug.
$



More information about the users mailing list