From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-81315-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 4592 invoked by alias); 27 May 2011 07:56:22 -0000
Received: (qmail 4581 invoked by uid 22791); 27 May 2011 07:56:21 -0000
X-SWARE-Spam-Status: No, hits=-0.4 required=5.0	tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_WEB,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout23.012.net.il (HELO mtaout23.012.net.il) (80.179.55.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 May 2011 07:56:01 +0000
Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0LLU00H00GMOBD00@a-mtaout23.012.net.il> for gdb-patches@sourceware.org; Fri, 27 May 2011 10:55:59 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([77.126.221.158]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LLU00HJSGP92A70@a-mtaout23.012.net.il>; Fri, 27 May 2011 10:55:59 +0300 (IDT)
Date: Fri, 27 May 2011 07:56:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [RFC] canonical linespec and multiple breakpoints ...
In-reply-to: <m3oc2pxjds.fsf@fleche.redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83k4dcd1bh.fsf@gnu.org>
References: <20110505162855.GA2546@adacore.com> <m3oc3gx48l.fsf@fleche.redhat.com> <83bozgmhil.fsf@gnu.org> <m3oc2pxjds.fsf@fleche.redhat.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2011-05/txt/msg00626.txt.bz2

> From: Tom Tromey <tromey@redhat.com>
> Cc: brobecker@adacore.com, gdb-patches@sourceware.org
> Date: Thu, 26 May 2011 15:05:35 -0600
> 
> Tom> While looking into this area I made a list of difficulties and
> Tom> considerations that I know of.  I can write that up in a readable form
> Tom> if you think that would help.
> 
> Eli> Please do, and thanks.
> 
> Here are the issues I know of.  I am not convinced that there is any
> good way to get all the desirable features into a single model, but I
> welcome brainstorming to this end.

Thanks.  If others have more issues and considerations to share,
please do.

I think the next step is indeed to come up with a model for handling
these issues.  If we cannot come up with a single model for
everything, we could try 2 models (a-la your "multi break" command).

Maybe a useful interim step would be reworking the description you
posted into a concise list of broad use case classes and issues that
need to be solved in each class.  We can then brainstorm possible
solutions against that list.