On Saturday 03 Jan 2004 6:44 pm, John Richard Smith wrote:It will not make any difference updating it, this bug has been around 2 years or more to my certain knowledge. What ever it is it's specific to mencoder ripping certain dvd CD's not others. I would say about 20to40% of my rips end up like this , the rest are just fine. Now I have some reason to suppose that it is an issue to do with how mencoder rips AC3 sound, which is dolby's surround sound. Sometimes it makes a dogs breakfast of encoding and creating the all important index file. The finished result, indeed the example given , the one that created the core dump in question, finishes, even though it made a core dump, but there is no index file, at least no index file that mplayer or any ofther mpeg4 stand alone multiformat dvd player can find. The result is that the stand alone players cannot play the CD's but mplayer can, as it has the built in ability to create a temporary index file by means of an index scan before it goes on to play it. It's annoying, but nothing morethan that, that mplayer has to do this, but it's absolutely critical that the stand alone players cannot as a result play the mencoder ripped CD's created in this way.
#0 0x081b5fb8 in ff_combine_frame () (gdb) ------------------------------------------------------------------- later ===== I should of read your email more carefully
#0 0x081b5fb8 in ff_combine_frame ()
(gdb) backtrace
#0 0x081b5fb8 in ff_combine_frame () = hexadecimal address ?
#1 0x40d5df40 in ?? () = source code address ?
The problem occurred at address 0x81b5fb8 which is in function ff_combine_frame. There is no other valid address on the stack, which means that either the bug wrote rubbish over the stack, or ff_combine_frame is the top level of a thread.
(gdb)
which makes more sense. But how do I use it ?
I mean what do I do next ?
Unless you want to debug the C yourself, nothing. I would do nothing with this version, I'd get the latest first.
Yes, but it's only worthwhile if you want to look through the C source code yourself.
Is that difficult ? How do I look for the address ?
Hmm,
I see, I don't know how to do that sound way beyond my ability as of this time, but I game ?
That's a steep learning curve. The Pentium datasheet is a book 2 inches thick.
It won't be, I've already looked, it's known but the developers are unable to simulate the problem, which means to my mind that it is a bug which is also CD related , ie you have to have the DVD that causes the problem, to simulate how it does a signal 11 core dump. On yet another disc it just simply won't happen, the problem is disc related to the mencoder programme. I mean , I would hardly want to be bothered to stay with mplayer/mencoder if every DVD ended up the same way, would I ? But it doesn't. About 60 to 80% are just fine, it's the minority of CD's that are the problem.
I guess I really ought to ask for help, but ?
Have you ever tied the mplayer people , need I say more ?
Seems to me I need to ask, but in a prepared way.
It's no use just sending them the core dump, for istance, together
with the my mencoder output ?
I know for a fact I'm not the only person with this problem, but most people feel intimidated by the developers.
Richard , how would you go about it ?
They are normally really nice people. The best way to go about it is to
1. Read all the documentation and install the latest CVS version. http://www.MPlayerHQ.hu/homepage/design6/info.html#docs says:
"Sending bugreports
First try the development (CVS) version too, maybe your bug is already known and fixed,
The bug reporting section is at http://www.MPlayerHQ.hu/DOCS/HTML/en/bugreports.htmlBeen a member some time, cannot understand much of it, they are really only well healed software types who know their way around the code.Essentially they are fixers themselves who supply solutions , rather than newbies like me who have a problem but cannot even begin to write a solution. Nothing wrong with that as such, but I, like others, have this problem that will have to be addressed someday.
2. Generate the crash in gdb as detailed in the above URL and grab all output.
3. Subscribe to the mplayer-users mailing list. Listen for a day or two and/or read the archives to get a hang of the etiquette.
Unless the problem is addressed mplayer/mencoder will fall into disuse as more and more dvd stand alone multi format players become the norm. Mine plays mpeg2 mpeg4/5 , mp3 discs, jpeg, and some VCD stuff I don't know anything about.
The windblows programme Gordian Knot rips these same mencoder core dumped CD's well, and the stand alone players play them, but mencoder ripped CD's with no index files don't work at all.
My idea was to assemble all I can to provide as much infomation as possible, including the name of the DVD, the mencoder script, the core dump, your core dump data etc etc, some hardware details, and mplayer/mencoder version numbers etc. and leave it to the experts. But whether anything will come of it I don't know. I have a suspicion it won't even be listed. It's that sort of list, only for the chosen. I have tried asking some questions before and they simply don't appear on the list, and so there is obviously some sort of filter.
4. Post a full description of the problem together with the gdb output and the version numbers of everything that may make a difference, especially your Linux distribution, kernel build and mencoder version. Offer to post the file that causes the problem, (I imagine it's a bit large for a public mailing list.) It's probably a good idea to mention any mencoder versions that you have seen to fail.
Anyhow , how do you look up the address on the code ? John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
