Joseph Heled wrote:
But the real problem is that by the time the plugin dialog is up lots of interesting stuff has already happened. So, how can I debug run() itself in a reasonable way?
(I can think of several ugly hacks to make run() stop and wait until I attach to it, but I still hope there is something I overlooked and there is a simple solution for that).
Please read http://developer.gimp.org/debug-plug-ins.txt . This file is also contained in the devel-docs/ directory in the source tree.
Philip
