[patch gdb]: Fix some DOS-path related issues in gdb

[Kai Tietz]

2011/3/3 Pedro Alves <pedro@codesourcery.com>:
> On Thursday 03 March 2011 14:58:32, Joel Brobecker wrote:
>> > I didn't know that the Windows 64bit target can use ELF debug info.
>> > Can it?  With what toolchains?
>> >
>> > As for mdebugread.c, I always thought it was MIPS specific.  What
>> > other platforms use it?
>>
>> These would still be pertinent in the case of cross debugging, no?
>> If the files were cross-compiled on Windows, the debug info would
>> contain file paths that follow the Windows convention...
>
> And then if you try to debug that on GNU/Linux, things still
> won't work, because filename_cmp changes behavior depending on host,
> not target or context.  That's why I believe there should be a clear
> distinction between what's a source path, and a host path.  I think
> Kai's bfd changes affect host paths, so they're fine. (haven't really
> checked, but that's what I imagine).  For source paths, I'd rather
> have this patch resurected...
>
>  <http://sourceware.org/ml/gdb-patches/2010-12/msg00343.html>
>
> I haven't looked at Kai's patch to see if it affects host
> paths or source paths.
>
> --
> Pedro Alves
>

Well Pedro,

this is exactly the point I described in my reply to Eli. The
debugging of cross-compiled binaries via systems with different
filename/path representation was and is still not operating. Here it
would be necessary to provide host<->creator information for doing a
mapping. And this isn't handled by this patch.
But at least this patch takes care that stuff compiled on a host with
host-compiler using DOS-paths is able to operate correct. And ELF is
an object-file format and has in principle nothing to do with unix and
can be used (with loader-support) on any specifc OS.

Kai