From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21207 invoked by alias); 25 Mar 2013 17:14:47 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 19911 invoked by uid 89); 25 Mar 2013 17:14:40 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 25 Mar 2013 17:14:40 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r2PHEbJi009032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 25 Mar 2013 13:14:37 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r2PHEaJF010463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 25 Mar 2013 13:14:36 -0400 From: Tom Tromey To: Hui Zhu Cc: Keith Seitz , Hui Zhu , gdb-patches ml Subject: Re: [PATCH] Fix create pending breakpoint handle extra_string issue if not parse_condition_and_thread References: <514E8D6C.2010606@mentor.com> <514EEB43.6040101@redhat.com> Date: Mon, 25 Mar 2013 19:32:00 -0000 In-Reply-To: (Hui Zhu's message of "Mon, 25 Mar 2013 11:45:38 +0800") Message-ID: <87620ftn9f.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-03/txt/msg00944.txt.bz2 >>>>> "Hui" == Hui Zhu writes: Hui> I am sorry that what you care about is the issue that affect the mi. Hui> But my patch is for the issue inside the function create_breakpoint. In this case, it seems to me that the API must be a bad one. Can't we just tell callers, "don't do that"? To me it seems like a pathological case. Tom