search

sleyzerzon / soar

Automatically exported from code.google.com/p/soar
1 stars 0 forks source link

Spawn Debugger doesn't work unless bin is on system path #81

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
If an SML client calls Agent::SpawnDebugger(), but the Soar bin folder isn't on 
the system path, the debugger silently fails to start. I've only tested this on 
Windows.

I think one solution is to modify the debugger to use java.library.path to load 
libraries rather than relying on the system path. For this to work, because of 
lib dependencies, the debugger would have to manually load the libraries before 
any code in sml.jar is loaded:

        System.loadLibrary("ElementXML");
        System.loadLibrary("SoarKernelSML");
        System.loadLibrary("Java_sml_ClientInterface");

Then Agent::SpawnDebugger() could easily add -Djava.library.path to the 
debugger startup command it builds.

Original issue reported on code.google.com by dave...@gmail.com on 29 Jul 2010 at 5:19