From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-26048-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 27866 invoked by alias); 11 Aug 2006 16:17:36 -0000
Received: (qmail 27853 invoked by uid 22791); 11 Aug 2006 16:17:35 -0000
X-Spam-Check-By: sourceware.org
Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 11 Aug 2006 16:17:28 +0000
Received: from HOME-C4E4A596F7 (IGLD-80-230-150-252.inter.net.il [80.230.150.252]) 	by romy.inter.net.il (MOS 3.7.3-GA) 	with ESMTP id FMG21452 (AUTH halo1); 	Fri, 11 Aug 2006 19:17:20 +0300 (IDT)
Date: Fri, 11 Aug 2006 16:17:00 -0000
Message-Id: <ufyg3dz6y.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
In-reply-to: <20060811134842.GA19749@nevyn.them.org> (message from Daniel 	Jacobowitz on Fri, 11 Aug 2006 09:48:43 -0400)
Subject: Re: How to set a breakpoint in file, which name has spaces?
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <uk65jdpoy.fsf@gnu.org> <44D8E404.5050407@Sun.COM> <ufyg6ewy9.fsf@gnu.org> <44D98D66.9060202@sun.com> <44DAD087.30004@sun.com> <20060810125827.GA18306@nevyn.them.org> <44DB6093.4030905@sun.com> <20060810175119.GA26275@nevyn.them.org> <44DC151F.3030009@sun.com> <ulkpve8j7.fsf@gnu.org> <20060811134842.GA19749@nevyn.them.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2006-08/txt/msg00104.txt.bz2

> Date: Fri, 11 Aug 2006 09:48:43 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Nikolay.Molchanov@Sun.COM, gdb@sourceware.org
> 
> > Daniel, should we update the manual in some way, or is this a bug that
> > should be fixed?
> 
> That's a good question :-)  This all comes down to decode_line_1.  The
> question of whether to change its parsing or document its quirks is
> beyond me, I'm afraid.  I'm reluctant to try touching that code.

Okay, I will document it, then.

> I wonder if, for some major version bump, we should document a new
> syntax for referring to source locations and implement it from
> scratch?

That sounds like a good idea.  Joel, perhaps you could kindly remind
us about this when ``some major version bump'' will be around the
corner.