Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: eliz@gnu.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Retrieve libraries from remote target
Date: Fri, 09 May 2008 23:58:00 -0000	[thread overview]
Message-ID: <200805091928.m49JSl0X018948@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <umyn0m0uz.fsf@gnu.org> from "Eli Zaretskii" at May 09, 2008 09:45:56 AM

Eli Zaretskii wrote:
> > Date: Thu, 8 May 2008 22:21:56 +0200 (CEST)
> > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> > 
> > The user interface is simple: if the path specified as "sysroot" starts
> > with the string "remote:", the sysroot location is assumed to be on the
> > remote target.
> 
> What if my _local_ "sysroot" happens to begin with the literal string
> "remote:"?  How can I tell GDB this is not a remote location?

You cannot.  Is this limitation a real problem?

> > +	  error (_("Could not open `%s' as an executable file: %s"),
> > +		 temp_pathname, bfd_errmsg (bfd_get_error ()));
> 
> In other error messages, you used "..", not `..', to quote file names.
> I like `..' better, and I think we use `..' in more places than we use
> "..".  I think consistency is important in user messages.

All messages in my patch were just copies from one place to another;
but I agree that they should be consistent.  I'll change everything
to use `..'.

> > +  if (strlen (bfd_get_filename (abfd)) >= SO_NAME_MAX_PATH_SIZE)
> > +    error (_("Full path name length of shared library exceeds \
> > +SO_NAME_MAX_PATH_SIZE in so_list structure."));
> 
> Is this really a useful message, especially since we don't show the
> actual value of SO_NAME_MAX_PATH_SIZE and the actual length of the
> file name?  I say either show the two numbers explicitly, or just tell
> it's too long.  (Yes, I know you only made a minor modification of an
> existing message.)

I think just "Shared library file name is too long." or something
similar would be enough; the user cannot really do anything in that
situation anyway ...

> Also, GNU coding standards frown on using "path name", they want us to
> use "file name".  If you do that, I think you can lose the "Full"
> part.

OK.

> Finally, this needs documentation before it is committed.

Sure, I'll add that.


Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-05-09 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09  1:45 Ulrich Weigand
2008-05-09  1:47 ` Daniel Jacobowitz
2008-05-09 12:59 ` Eli Zaretskii
2008-05-09 23:58   ` Ulrich Weigand [this message]
2008-05-10  9:12     ` Eli Zaretskii
2008-05-10 12:48       ` Ulrich Weigand
2008-05-10 17:22         ` Eli Zaretskii
2008-05-11 22:20           ` Daniel Jacobowitz
2008-05-12 20:07             ` Eli Zaretskii

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=200805091928.m49JSl0X018948@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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