From 4aed2c8219774f5d797760606b8489a92ddc5163 Mon Sep 17 00:00:00 2001 From: toma Date: Wed, 25 Nov 2009 17:56:58 +0000 Subject: Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features. BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdebase@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- nsplugins/HOWTO.DEBUG | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 nsplugins/HOWTO.DEBUG (limited to 'nsplugins/HOWTO.DEBUG') diff --git a/nsplugins/HOWTO.DEBUG b/nsplugins/HOWTO.DEBUG new file mode 100644 index 000000000..d00b4a5a6 --- /dev/null +++ b/nsplugins/HOWTO.DEBUG @@ -0,0 +1,22 @@ +Want to run nspluginviewer in valgrind? It's not easy. Here's how: + +- Trigger the plugin you want in konqueror without valgrind running. +- ps awwww | grep nspluginviewer +- Record the commandline, then kill -11 the process +- close drkonqi +- in a konsole, export ARTSDSP_MMAP=1 + - run LD_PRELOAD=$KDEDIR/lib/libartsdsp.so.0:$KDEDIR/lib/libartsc.so.0 valgrind -v --num-callers=15 --error-limit=no nspluginviewer + +- WAIT for four lines to be printed to the screen that start with: +5 ............ +6 ............ +7 ............ +8 ............ + +- QUICKLY go back to konqi, reload the plugin page. +- You should see the valgrind konsole start to scroll lots of debug output. If + it does not, then it probably not picking up the new nspluginviewer. Try + again. +- As long as you don't close this konqueror window, you should be able to keep + rerunning valgrinded nspluginviewer without much trouble. + -- cgit v1.2.1