This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch gdb]: Fix some DOS-path related issues in gdb
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Joel Brobecker <brobecker at adacore dot com>, Eli Zaretskii <eliz at gnu dot org>, Kai Tietz <ktietz70 at googlemail dot com>
- Date: Thu, 3 Mar 2011 15:32:19 +0000
- Subject: Re: [patch gdb]: Fix some DOS-path related issues in gdb
- References: <AANLkTi=QoOiBg3XmMv+hRNe8DkT2YiVGZ=7NhaQwzCey@mail.gmail.com> <E1Pv94S-000861-BZ@fencepost.gnu.org> <20110303145832.GY30306@adacore.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