Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Denis PILAT <denis.pilat@st.com>
Cc: Doug Evans <dje@google.com>, Michael Snyder <msnyder@vmware.com>,
		Jon Beniston <jon@beniston.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Patch to support spaces in filenames & paths
Date: Thu, 04 Dec 2008 13:11:00 -0000	[thread overview]
Message-ID: <20081204131028.GA24868@caradoc.them.org> (raw)
In-Reply-To: <4937A4E3.4040609@st.com>

On Thu, Dec 04, 2008 at 10:37:39AM +0100, Denis PILAT wrote:
> Actual implementation of append/dump/restore does not accept spaces at  
> all, except in the last argument, and I think it's just a side effect.
> To me comma must not be considered as a separator since dump command  
> accepts expression and the calculation of START , END address or OFFSET  
> is often a function call like sizeof (), but can be more than that like a 
> function that takes more than one parameters, "max(a,b)" or whatever.

I don't think it applies here, but take a peek at the function Doug
mentioned - it does handle nested commas.  It's not perfect, but it's
pretty good.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-12-04 13:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02 13:09 Jon Beniston
2008-12-02 21:20 ` Michael Snyder
2008-12-02 23:38   ` Daniel Jacobowitz
2008-12-03  0:04     ` Pedro Alves
2008-12-03  0:26     ` Doug Evans
2008-12-04  9:38       ` Denis PILAT
2008-12-04 13:11         ` Daniel Jacobowitz [this message]
2008-12-10 15:32           ` Denis PILAT
2008-12-10 16:20             ` Daniel Jacobowitz
2009-01-05 14:20               ` Denis PILAT

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=20081204131028.GA24868@caradoc.them.org \
    --to=drow@false.org \
    --cc=denis.pilat@st.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jon@beniston.com \
    --cc=msnyder@vmware.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