debugger issues

[killerbot]

linux, rev 9212

Actually there are most probably 2-4 issues.

First : the goal :
Application which is a service, and can be (nicely) stopped by hitting ctrl-c (aka SIGINT).

Alternative 1 :
start the debugger, and try to enter in the "Debugger"-Tab, in the "command" entry "signal SIGINT"
==> not possible, the field doesn't want to take focus, so nothing can be entered

workaround : pause debugger ==> then you can put the focus on the field [PROBLEM : you can not copy/paste into it], and type it in

Alternative 2 :
Settings -> debugger -> Default -> Debugger initialization commands : add "handle SIGINT nostop print pass"
start the debugger and do the ctrl-c ==> debugger seems to do something (console window disappeared), pause/stop button still enabled
press the pause button => seems the ctrl-c gets processed and the clean (destructor path ..) gets being executed



Expected behavior :
Alternative 1 :
- allow copy/paste in the "command" field
- be able to type in it even while running (?)

Alternative 2 :
- would expect to no longer need to press pause

[oBFusCATed]

- allow copy/paste in the "command" field

Works here, at least I can ctrl+v something copied from the editor. But this is a problem caused by wxGTK unfortunately.

- be able to type in it even while running (?)
- would expect to no longer need to press pause

I don't think it is safe. The commands canbe executed only if the debugger has pause the debuggee.
So the plugin should do a pause, which is not as reliable operation as I want it to be.

[crobar]

- allow copy/paste in the "command" field

Works here, at least I can ctrl+v something copied from the editor. But this is a problem caused by wxGTK unfortunately.

Doesn't (and has never) worked for me on multiple platforms, it's quite a frustrating niggle. I wish the right-click menu offered the paste option as an alternative.

[oBFusCATed]

Argh... I hate this part of wx and c::b....