Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Re: Remote testsuite problem: invalid executable cache
Date: Tue, 26 Jul 2011 01:01:00 -0000	[thread overview]
Message-ID: <4E2DE2EB.6020402@earthlink.net> (raw)
In-Reply-To: <201107251740.p6PHeL3s020964@d06av02.portsmouth.uk.ibm.com>

On 7/25/11 10:40 AM, Ulrich Weigand wrote:
> Mark Kettenis wrote:
>
>>> +mi_gdb_load ${binfile}-c++
>> Using the '+' character in filenames may not be the best idea.
> Is this really a problem?  I thought '+' was supported just about
> everywhere ...  (There's filenames containing '+' in the GDB source
> repository, for example.)

I would be inclined to avoid '+' myself, not because of the filesystem, 
but because of potential tcl/dejagnu regexp hell.  (Yes, it can be 
worked around, but it gets annoying when 54 backslashes in a row is not 
enough :-) )

Stan
stan@codesourcery.com


  reply	other threads:[~2011-07-25 21:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 15:22 Ulrich Weigand
2011-07-22 16:35 ` Jan Kratochvil
2011-07-22 16:53 ` Daniel Jacobowitz
2011-07-22 17:53   ` [rfc] " Ulrich Weigand
2011-07-22 18:40     ` Tom Tromey
2011-07-22 18:56       ` Ulrich Weigand
2011-07-24 18:04     ` Mark Kettenis
2011-07-25 18:33       ` Ulrich Weigand
2011-07-26  1:01         ` Stan Shebs [this message]
2011-07-26 17:31           ` [rfc] Avoid '+' in file names (Re: [rfc] Re: Remote testsuite problem: invalid executable cache) Ulrich Weigand
2011-07-26 18:20             ` Tom Tromey
2011-07-26 19:20               ` Ulrich Weigand

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=4E2DE2EB.6020402@earthlink.net \
    --to=stanshebs@earthlink.net \
    --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