gDEBugger error message on startup.

[SabelaVega]

Well, this is a new one on me!



I sure don't remembering copying a gDEBugger Server into my "javaw" application directory. Maybe one of my development tools did?

Then, it shows this:


Ah, good grief.

Does anyone have any suggestions that don't involve, "Uninstall and reinstall Java?" Every time I do that, I end up fighting for four hours to get Eclipse working properly again. I can't afford to have my development tools break, just because I want to play a game.

[MagicManICT]

Check the program's documentation about turning it on and off when you don't want to use it. It's not a matter of whether Salem is breaking your debugging tool, I don't think, but more a matter of your debugging tool interfering with the normal operation of Java when you don't want to use the tool.

You might try setting the Salem shortcut to use java.exe. This might get around the debugger's check. You may only need to modify the shortcut, or you might need to modify the .jnlp file

[SabelaVega]

Check the program's documentation about turning it on and off when you don't want to use it. It's not a matter of whether Salem is breaking your debugging tool, I don't think, but more a matter of your debugging tool interfering with the normal operation of Java when you don't want to use the tool.

Yeah, I just don't remember setting it up, in the first place! Huh. Maybe I've been profiling games in my sleep. That would explain the strange dreams.

You might try setting the Salem shortcut to use java.exe. This might get around the debugger's check. You may only need to modify the shortcut, or you might need to modify the .jnlp file

Yeah, that's what I was thinking. I have a mess of JRE versions installed, so I have a lot of other potential java options. I'm going to try tweaking my shortcut, because I think that'll do the job. I'll report back after I have time to test it!