Hey Steve,
Well, I'm glad you've managed to hack around the limitations ;)
Sorry about the delay, I was nursing a bad tooth.
Ouch!
I agree that it is irritating to have to specify debug.target
in the user properties, in those important cases where
scite-gdb can't guess the target. Any suggestions would be
welcome!
As I mentioned, I got debug.target to work by specifying it in a
SciTEDirectory.properties file in the directory that contains the
source files for the app.
It was easy to reproduce the problem, and to find a hack:
just put double-quotes around the debug.target:
debug.target="c:\Program Files\SciTE Test\test1.exe"
But here's the proper fix! In gdb.lua, after line 273
where the target has just been discovered, insert:
if find(target,"%s") and sub(target,1,1) ~= '"' then
target = '"'..target..'"'
end
I've not had an issue with spaces in the debug.target, the problem I'm
having is with spaces in SciTEDefaultHome, so my wscite directory
(containing SciTE.exe), needs to be in a path that doesn't contain
spaces (i.e. right off the root).
I will have a new improved version of scite-gdb available on
Monday:
...
- All those commands in the Tools menu are filled in only when
they're needed (after launching the debugger for the first
time)
Sounds cool, but I'm not sure if I understand. Does this mean the
commands in the Tools menu won't show until you activate the debugger?
If so, how do you activate the debugger? When you kill the
debugging session, will the commands also disappear?
Also, would it be possible for 'Breakpoint' to toggle the breakpoint?
I've noticed that I can set a breakpoint but I can't clear it (unless
I'm missing something).
I very much appreciate the integration of gdb in to SciTE and I look
forward to the next version!
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
