[MPlayer-users] intel os x crash using window codecs

[The Wanderer]

Dave Chand wrote:

> 
> On Nov 30, 2006, at 8:32 PM, The Wanderer wrote:
> 
>> Please compile MPlayer with --enable-debug, read
>> DOGS/HTML/en/bugreports.html and follow the appropriate
>> instructions.
>> 
> Yes mplayer was compiled with debugging symbols. "-gfull" on OS X

I didn't say "compile with debugging symbols"; I said "compile with
--enable-debug", as in, pass the '--enable-debug' option to MPlayer's
configure script before compiling. (It's possible that you did do that,
but nothing I have yet seen indicates that you did.)

>> Specifically, provide the exact command line you used,
> 
> the command line was simply mplayer -v tumble.wmv

Acknowledged - but it's better to be explicit about this in every case.

>> the full (un-snipped) output of MPlayer, and the output of gdb from
>> the  commands given in the crash-bugs section of that file (not
>> just the 'bt  full' you did provide).
> 
> I hope both of these are provided below.

<snip>

No, they aren't:

> (gdb) bt ful

I said, NOT just 'bt full'; the output of the various commands described
in the "crashing bugs" section of DOCS/HTML/en/bugreports.html. The full
correct bug-reporting procedures can be found in that file and its
relatives.

As Zuxy Meng implied, this will include a 'disass $pc-32 $pc+32'. It
also includes other commands, but I'm not going to provide them here,
because I want you to actually read the document.

>> (...are the Win32 codecs supposed to work under MacOS X anyway...?
>> maybe if it's an Intel Mac...?)
> 
> No not really. I am just trying to help whoever is working on getting
> win32 codecs to work under os x. I will admit this might be a
> premature thing.

There's nothing wrong with that, but it is better to mention things like
that, so that people don't assume that you're just looking for help.

(Also, in case you weren't aware: the Win32 codecs are binary, and as
such are architecture-dependent. They may potentially be able to work on
an Intel Mac, but AFAIK they fundamentally cannot work on a non-x86
system unless run via a full emulation layer.)

> Some files with assembly optimizations needed to be compliled with -
> fomit-frame-pointer, in order for the compilation to go through.

If by this you mean "I didn't compile with --enable-debug because of
this problem", then all I have to say for the moment is that you should
have started out with a bug report of *that* problem, with possibly a
side note mentioning what you were trying to accomplish which led you to
want to compile with --enable-debug.

As it happens, this problem is known, but I do not know what the status
of a fix is.

-- 
       The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.