On Sunday 04 Jan 2004 10:07 am, John Richard Smith wrote: > Richard Urwin wrote: > >You have tried the -idx flag to mencoder? > > Oh gosh yes, always include it without fail,
Not quite: On Saturday 03 Jan 2004 6:44 pm, John Richard Smith wrote: > Core was generated by `mencoder dvd://1 -ovc lavc -lavcopts > vcodec=mpeg4:vhq:vbitrate=1024 -oac mp3lam'. > >On Sunday 04 Jan 2004 12:25 am, John Richard Smith wrote: > >>Anyhow , how do you look up the address on the code ? > > > >You already have the function where the fault occurs so a simple search of > > the source code will find that function. > > When you say search the code, do you mean the installed binaries or the > unpacked tar ball ? or what ? The source code, of course. > >For a more precise answer build the application as given on the How To > > Produce a Bug Report page. > > You mean recompile the unpacked tar ball with instrutions on debugging > in the readme ? > Or possibly you are refering to mplayer website instructions ? Extract the source code from the tar ball. Recompile the source code with the flag on the ./configure command as given on the mplayer website documentation under how to submit a bug report. http://www.mplayerhq.hu/DOCS/HTML/en/bugreports_what.html#bugreports_crash > >Then when you run it under gdb, > > Or are you saying after the ./confure , and make, but before make > install, run gdb on the install file which lies somewhere in the source > directory ? Not the install file, the application. The make command creates the application, make install just moves it into the right place. The documentation recommends running it before the make install, but probably only so the command is simpler: "gdb ./mplayer" rather than "gdb ./usr/local/bin/mplayer" or some such. It also avoids replacing your currently installed version. In your case I would imagine it will be "gdb ./mencoder" of course. -- Richard Urwin
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
