From: Pedro Alves <pedro@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, zulliger@indel.ch
Subject: Re: proposal: substitute-path handles foreign dir separators
Date: Fri, 17 Dec 2010 19:44:00 -0000 [thread overview]
Message-ID: <201012171943.56895.pedro@codesourcery.com> (raw)
In-Reply-To: <83vd2sfbkl.fsf@gnu.org>
On Friday 17 December 2010 19:23:22, Eli Zaretskii wrote:
> Thanks. I have 2 comments:
>
> . if we are going to add this, it needs documentation
For sure. I only posted what I had because the subject came up, not
because I considered it completely finished.
> . why only source file names? the issue is relevant to any file name
Can you give an example? My thinking is/was we should keep target paths, host
paths and source paths separate worlds. Target path comparisions are handled
with "set/show target-file-system-kind". Host paths should be compared with
other host paths using FILENAME_CMP, which uses the appropriate native
host compare function. The source paths setting is for the case of
e.g., a arm-linux program that was compiled on a Windows machine,
and is later debugged on an x86-linux host gdb (against a arm-linux
gdbserver). You want gdb to consider the target filesystem of unix
kind, but, you want source path comparisions with paths embedded in
debug info to be permissive by using dos style path comparisons.
--
Pedro Alves
next prev parent reply other threads:[~2010-12-17 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 14:18 Raphael Zulliger
2010-12-17 15:26 ` Eli Zaretskii
2010-12-17 17:50 ` Pedro Alves
2010-12-17 19:23 ` Eli Zaretskii
2010-12-17 19:44 ` Pedro Alves [this message]
2010-12-17 20:11 ` Pedro Alves
2010-12-20 7:41 ` Raphael Zulliger
2010-12-22 12:00 ` Pedro Alves
2010-12-20 6:38 ` Raphael Zulliger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201012171943.56895.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=zulliger@indel.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox