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: Fri, 23 Apr 2010 14:35:00 -0000	[thread overview]
Message-ID: <83ljce2q5c.fsf@gnu.org> (raw)
In-Reply-To: <201004231146.22671.pedro@codesourcery.com>

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Fri, 23 Apr 2010 11:46:22 +0100
> Cc: gcc-patches@gcc.gnu.org
> 
> Oh.  I really meant a "path", as in:
> 
>  "A path, the general form of a filename or of a directory name, specifies a unique
>  location in a file system."
> 
>  (From <http://en.wikipedia.org/wiki/Path_%28computing%29>.)
> 
> I suppose that's why we have IS_ABSOLUTE_PATH, and not IS_ABSOLUTE_FILE_NAME,
> and such.
> 
> IMO, it's the use of singular path or "search path" to mean
> "list of directories" that's overloaded.
> "Set assumed file system kind for target reported file names"
> kind of sounds like it is only talking about the filename "/dir1/dir2/files1"
> (or directory and filenames, if you think of a directory a file as well).
> Maybe I could just get rid of the mention of paths/file names, and go with:
> 
>   "Set the assumed file system kind of the target."
> 
> Anyway, I'll change it to what you think is clearer.

Not only is it clearer, it's in GNU coding standards, see my other
mail.

>   c:/foo/bar.dll ==> /path/to/sysroot/foo/bar.dll
> "
> 
> I'll be happy to clarify this in the docs, if you think it's useful.

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.

> I suppose that'll be ... in `i386_go32_init_abi'.

Yep.

> (Why are DJGPP specific things in the generic i386-tdep.c, BTW?)

History, I think.  The number of architecture specific bits is quite
small.

> >   @cindex DOS file-name semantics if file names.
> 
> Will do.  I'll assume you meant s/if/of/.

Of course.

Thanks.


  parent reply	other threads:[~2010-04-23 14:35 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 [this message]
2010-04-24 11:18       ` Pedro Alves
2010-04-24 11:40         ` Eli Zaretskii
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=83ljce2q5c.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