Thanks for the reply. I looked carefully at your video and I think it describes what I am doing on a daily basis.
I can start Netbeans to debug my code and put breakpoints to my heart’s content. That works very well.
What I am doing is starting an instance of ImageJ in debug mode. Then I send it off to run my plugin, capture it at a breakpoint, and I can find whatever the problem is.
Here I want to do something slightly different. I want to start the nominal version of Fiji in exactly the same way my users do. Then I attach the Netbeans debugger to the nominal software as the end user is actually using it.
The documentation says to use:
Note that it is using linux64 in the example. In fact Linux works perfectly well. As I wrote in the first part of the thread, the command box shows that it is still in command and ImageJ is listening for an attached debugger.
In Windows it seems to be to be broken (or it never actually worked - don’t know which). The command box does indeed start Fiji, but then it returns to the command prompt without saying it is listening. When I try to attach the debugger, it say connection refused. That makes some sense if ImageJ isn’t really listening for a connection.
What I actually use in Windows is
There are 2 different versions of the command string and I tried them both. The first one is similar to the linux version, except using ImageJ-win32.exe, and I chose a slightly different port as well. This one will return to the command prompt as soon as Fiji is running. Trying to attach the Netbeans debugger will result in connection refused.
Then I tried the second version. That basically hung in an endless loop, but didn’t allow me to attach a debugger either. I basically killed the Fiji process and then it returned to the command prompt.
It is a VERY nice feature that I can attach a debugger from Netbeans or Eclipse to the nominal software. It is a real pity that it doesn’t seem to work in Windows (or at least I can’t figure out how to do it).