[PATCH] Facilitate remote debugging with gdb

[Vladimir Prus]

On Saturday 05 September 2009 Nicolai Hähnle wrote:

> The attached patches are against a number of issues I've run into when trying 
> to use remote debugging. 

Nicolai,

thanks for the patches. I will try to review them next week.

> They are sorted roughly by importance:
> 
> 1. The connected_to_program event is necessary to make sure kdevelop tells gdb 
> about breakpoints, so emit it.
> 
> 2. gdb needs to be told about the executable being debugged. While this can be 
> done in the remote setup script, forcing the user to do it is kind of silly 
> when we already know where the executable is. So the appropriate 
> FileExecAndSymbols command is set in all cases.
> 
> 3. When launching the remote program, we'd better know about the arguments 
> that the user has configured - so why not add them to the parameters of the 
> run script?
> 
> 4. The debugging shell functionality appears to be totally broken (it passes a 
> URI to QFileInfo which apparently only knows about local paths?). Replace it 
> by a possibility for adding additional parameters. Then people who need to use 
> such a shell for whatever reason can just use the shell as their gdb 
> executable.
> 
> Note: The gdbtest unit test seems to be broken, even in trunk? 

Yes. Although I have fixed a few failures I found, some still
remain, and the test run ends up with a segfault, even.

> At least it 
> fails For me with warnings about disappearing processes or something.

Those are warnings, not failures. There are real failures, though.

- Volodya