Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [gdb/libiberty] Improve support for cross debugging shared libraries with DOS style pathnames (from Unix hosts)
Date: Sat, 24 Apr 2010 11:40:00 -0000	[thread overview]
Message-ID: <83hbn113k9.fsf@gnu.org> (raw)
In-Reply-To: <201004241217.46557.pedro@codesourcery.com>

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sat, 24 Apr 2010 12:17:46 +0100
> Cc: gcc-patches@gcc.gnu.org
> 
> On Friday 23 April 2010 15:35:11, Eli Zaretskii wrote:
> > Not only is it clearer, it's in GNU coding standards, see my other
> > mail.
> 
> Okay, I changed all user visible strings, I think.

Thanks.

> > No, it's clear enough.  I just wondered why you didn't remove the
> > drive letter right away.  I guess that's common practice in some
> > quarters to mount DOS-ish filesystems that way.  I don't really mind
> > to support that if people are using it.
> 
> Hope you don't mind, I ended up extending the docs here to
> explicitly explain why the lookup algorith is the way it is,
> so that users don't wonder the same you did.

I don't mind, of course.  Thanks for the extra effort.

> I've moved that new target filesystem handling code to a
> new file, and, handled DJGPP's gdbarch.

Again, thanks.

> I think this updated patch addresses all your comments.  Could
> you please take a new quick look at this?

It's fine, I have only 2 minor nits to report:

> +Then, @value{GDBN} attempts prefixing the target file name with
> +@var{path}, and look for the resulting file name in the host file
> +system:         ^^^^

"looks"

> +@smallexample
> + @file{/path/to/sysroot/c/sys/bin/foo.dll}
> + @file{/path/to/sysroot/c/sys/bin/bar.dll}
> + @file{/path/to/sysroot/z/sys/bin/bar.dll}
> +@end smallexample
> +
> +and point the system root at @file{/path/to/sysroot}, so that

We need @noindent before the last line.


  reply	other threads:[~2010-04-24 11:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 17:24 Pedro Alves
2010-04-22 17:46 ` Daniel Jacobowitz
2010-04-23  8:54 ` Eli Zaretskii
2010-04-23 10:46   ` Pedro Alves
2010-04-23 11:15     ` Mark Kettenis
2010-04-23 14:30       ` Eli Zaretskii
2010-04-23 15:41         ` Mark Kettenis
2010-04-23 14:35     ` Eli Zaretskii
2010-04-24 11:18       ` Pedro Alves
2010-04-24 11:40         ` Eli Zaretskii [this message]
2010-04-24 13:13           ` Pedro Alves

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=83hbn113k9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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