Thread: [Mplayerplug-in-devel] how to debug the mplayerplug-in plugin ?
Brought to you by:
kdekorte
From: Greg H. <mp...@am...> - 2005-06-30 13:43:10
|
My 1st thought was to enable the DEBUG print statements in the plugin. I tried enabling "debug=1" in /etc/mplayerplug-in.conf, and got no output. So then I went thru the sources, and discovered the compile time PLUGIN_TRACE, in Makefile.in, so then I make a fresh directory, unpacked the source, change the CFLAGS line in Makefile.in (added -DPLUGIN_TRACE), did the configure, make, etc. During the build, I definately saw my "-DPLUGIN_TRACE" on each compile line. I installed the newly built plugin, and launched firefox, referenced an avi file, but did not see any output. I then launched mozilla, and again referenced an avi file, and again, did not see any output. both were launched from the command line, so I was expecting output to stdout. is this not correct ? Anyone here have experiance with this ? how do/did you debug the plugin ? thx, and best rgds, -Greg +---------------------------------------------------------------------+ Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log) | Greg Hosler gr...@ho... | +---------------------------------------------------------------------+ |
From: Kevin D. <kde...@ya...> - 2005-06-30 14:04:32
|
On Thursday 30 June 2005 07:45 am, Greg Hosler wrote: > My 1st thought was to enable the DEBUG print statements in the plugin. I > tried enabling "debug=3D1" in /etc/mplayerplug-in.conf, and got no output= =2E So > then I went thru the sources, and discovered the compile time PLUGIN_TRAC= E, > in Makefile.in, so then I make a fresh directory, unpacked the source, > change the CFLAGS line in Makefile.in (added -DPLUGIN_TRACE), did the > configure, make, etc. > > During the build, I definately saw my "-DPLUGIN_TRACE" on each compile > line. I installed the newly built plugin, and launched firefox, referenced > an avi file, but did not see any output. I then launched mozilla, and aga= in > referenced an avi file, and again, did not see any output. > > both were launched from the command line, so I was expecting output to > stdout. is this not correct ? > > Anyone here have experiance with this ? how do/did you debug the plugin ? > > thx, and best rgds, > > -Greg > Greg, In the /usr/bin/mozilla or /usr/bin/firefox scripts there is a line that lo= oks=20 like this # if there's no command line argument and there's not a running # instance then just fire up a new copy of the browser if [ -z "$1" ]; then exec $MOZ_PROGRAM $MOZARGS 2>/dev/null >/dev/null fi Change it to # if there's no command line argument and there's not a running # instance then just fire up a new copy of the browser if [ -z "$1" ]; then exec $MOZ_PROGRAM $MOZARGS=20 fi Since all of mplayerplug-in output goes to stdout. And mozilla dumps it all= =20 to /dev/null.... If you are still working on the mime-type issue... You won't see any=20 mplayerplug-in output anyway since the plugin is never called. Kevin |
From: Greg H. <mp...@am...> - 2005-06-30 14:20:38
|
On 30-Jun-2005 Kevin DeKorte wrote: > If you are still working on the mime-type issue... You won't see any > mplayerplug-in output anyway since the plugin is never called. hmm... then how does mozilla/firefox know to pass a file to a plugin ? is there, perhaps some mozilla/firefox registry that I need to put my file association into ? thx, and best rgds, -Greg +---------------------------------------------------------------------+ Please also check the log file at "/dev/null" for additional information. (from /var/log/Xorg.setup.log) | Greg Hosler gr...@ho... | +---------------------------------------------------------------------+ |