Re: [dsdp-dd-dev] Source lookup and remote debugging launch sequence

[Daniel Jacobowitz <drow@xxxxxxxxx>]

On Wed, Feb 20, 2008 at 09:08:57AM -0800, Pawel Piech wrote:
>    Hopefully we can handle these differences using appropriate source
>    containers.  If that's not enough, we'll need customized GDB-DSF services
>    for these different GDB variants.  This is OK, this is how DSF debuggers
>    are meant to be extended.

Careful of the abstraction layering here.  It's not (entirely) an
issue of GDB variants.  It depends more on the tools used to compile
the code you're debugging.  For instance, if you use a native Windows
toolchain to debug but your nightly builds run on a farm of Linux
systems, you'll get forwards slashes.

>    I'm not sure output to -break-insert will be that useful, since to insert
>    a breakpoint we need to know the correct path in the first place.  But I
>    assume that -stack-list-frames and -file-list-exec-source-files will
>    return correct full paths to use with the path mapping.

Right - as long as you've taught GDB where to find the sources it will
return fullnames in most contexts.

-- 
Daniel Jacobowitz
CodeSourcery