Hey All,
I've recently been working on a Lua extension which allows you to debug using gdb in your favourite code editor. It currently only works with extman, but it would not be difficult to extract the bits. It uses the ability of SciTE Lua to dynamically load shared libraries; the spawner library uses the Director interface to pass spawned gdb output back to the Lua subsystem.
I finally had some time to play with this, and I've run in to some issues: - I created a SciTEDirectory.properties in the directory containing the source code to the project I'm trying to debug, when I set a break point and 'Run' it still uses the filename of the currently focused file. The only way I could test debug.target was to set it in my SciTEUser.properties which is quite limiting - after successfully setting the debug.target in my SciTEUser.properties file, I get the following error: !cmd gdb --quiet -x C:\Program Files\wscite\scite-gdb/prompt.cmd -f C:\Source\emerge\trunk\Source\bin\emergeLauncher.exe setting status to running quitting gdb setting status to dead C:\Source\emerge\trunk\Source\emergeLauncher/C:\Source\emerge\trunk\Source\bin\emergeLauncher.exe: Invalid argument. - I assume scite_gdb doesn't like paths in the directory structure, because I get lots of errors with: C:\Program: No such file or directory. (I assume because I installed scite.exe to C:\Program Files\wscite) I really like the idea of being able to use GDB from within SciTE, so I'm hoping there is a way to fix these issues. Cheers! Chris -- Chris Sutcliffe http://ir0nh34d.googlepages.com http://ir0nh34d.blogspot.com http://emergedesktop.org _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
