diff --git a/DOCS/bugreports.html b/DOCS/bugreports.html index 109f1259ae..cafc919476 100644 --- a/DOCS/bugreports.html +++ b/DOCS/bugreports.html @@ -58,11 +58,15 @@ we will be unable to properly diagnose your problem otherwise.
An excellent and well written guide to asking questions in public forums is - How To Ask - Questions The Smart Way by Eric S. Raymond. If you follow these guidelines - you should be safe. But please understand that we all follow the mailing lists - voluntarily in our free time. We are very busy and cannot guarantee that you - will get a solution for your problem or even an answer.
+ How To Ask Questions The Smart Way + by Eric S. Raymond. There is another + called + How to Report Bugs Effectively + by Simon Tatham. If + you follow these guidelines you should be able to get help. But please + understand that we all follow the mailing lists voluntarily in our free time. + We are very busy and cannot guarantee that you will get a solution for your + problem or even an answer.config.hconfig.makGui/config.maklibvo/config.maklibao2/config.makconfigure.log.
+
If you have a core dump of the crash continue reading the next paragraph, - otherwise skip it.
- - -Please create the following command file:
- -disass $pc-32 $pc+32
- info all-registers
Then simply execute the following on your command line:
- - gdb mplayer --core=core -batch --command=command_file > mplayer.bug
You have to run MPlayer inside gdb and send us the complete
+ output or if you have a core dump of the crash you can extract useful
+ information from the Core file. Here's how:
bt
disass $pc-32 $pc+32
Please create the following command file:
+ +disass $pc-32 $pc+32
+ info all-registers
Then simply execute the following on your command line:
+ + gdb mplayer --core=core -batch --command=command_file > mplayer.bug