Thanks! That did not get me all the way there, but it was a start.
I set the host application like you suggested, to /usr/bin/python /my/path/start_debug.py . Then I would debug it, with the breakpoint set. When the debugger loaded, if I press "continue" or "next line", it exits nearly immediately with code 0. Instead, I have to:
1. Start debugger
2. In the user commands, 'file /usr/bin/python'
3. In the user commands, ''set args /my/path/start_debug.py' . By the way, the paste function does not work in the user commands, so I have to type this in
4. In the user commands, 'run'
Then it stops at the breakpoint.
Is this a bug, that I have to go through all that? If so, I'd like to report it, but I don't know nearly enough about C::B (or gdb, for that matter) to determine whether it's them, or me. According to the spec, what does the setting of the host translate to in GDB commands? I'll try to replicate it on naked GDB then, and see if it fails there too before submitting a bug.
Thanks!