From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10509 invoked by alias); 18 Apr 2014 20:39:21 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 10496 invoked by uid 89); 18 Apr 2014 20:39:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: mail-pb0-f51.google.com Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com) (209.85.160.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 18 Apr 2014 20:39:20 +0000 Received: by mail-pb0-f51.google.com with SMTP id uo5so1795267pbc.10 for ; Fri, 18 Apr 2014 13:39:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=N5lI5dY1ApA+fBUONm3zB7+1NL0vYwcX82/usn9nlr0=; b=PT2I4CppCH6C0hnG8Hw0+CoOdAOSrzBJD4VbcsSRwsT8GraW082FZOpJ8uU5UZLYIp 5bf/fKMvp/DokKcEAbLNsnGCSFfiJr6hguayN5aKccRc962Bxgym2SMJfTGiI5uyXB4O v9Lgbh9Zy3bb2pVfHwbmE2oQLjiabWTEtYOUSyVdzfF4ZY0vgoMJULnJgvIubSHLkJ3U RRqo68Vwit0bymzRgDoNXlIwbml5X1TXyJoyL8ljxCVU15weQK/gWLbGWt3p5BtUU381 Zwxt60e942xQHcB0lS6khkz8eX6h1nTv2IYvXUga0k5VxzQTbXEz9Vr/+647+IsJtvEi yOlg== X-Gm-Message-State: ALoCoQkr5QpbpblxMdj8oBAACD+h/OfK5lzgpLCkJqJdbe3qatDwFDcP5e8QCo9UectUI7bDWRC1 X-Received: by 10.68.201.226 with SMTP id kd2mr4096333pbc.157.1397853558555; Fri, 18 Apr 2014 13:39:18 -0700 (PDT) Received: from linux (ip68-9-64-242.ri.ri.cox.net. [68.9.64.242]) by mx.google.com with ESMTPSA id x5sm61745896pbw.26.2014.04.18.13.39.16 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 18 Apr 2014 13:39:17 -0700 (PDT) Date: Sat, 19 Apr 2014 08:28:00 -0000 From: Bob Rossi To: "Terekhov, Mikhail" Cc: "gdb@sourceware.org" Subject: Re: MI async status output Message-ID: <20140418203925.GB31328@linux> References: <5346B226.40209@cs.msu.su> <20140410201259.GA15060@linux> <5347BD84.5030200@broadcom.com> <20140412002538.GA27657@linux> <5350E049.9070705@codesourcery.com> <20140418104619.GA26892@linux> <53512470.8080305@codesourcery.com> <20140418163002.GA29631@linux> <535155F9.3030405@codesourcery.com> <84F432E8540221418FB3B2A59999A3610A3B6F6348@MX23A.corp.emc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <84F432E8540221418FB3B2A59999A3610A3B6F6348@MX23A.corp.emc.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2014-04/txt/msg00065.txt.bz2 On Fri, Apr 18, 2014 at 03:27:03PM -0400, Terekhov, Mikhail wrote: > > -----Original Message----- > > From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On > > Behalf Of Vladimir Prus > > Sent: Friday, April 18, 2014 12:43 PM > > To: Bob Rossi > > Cc: Andrew Burgess; gdb@sourceware.org > > Subject: Re: MI async status output > > > > On 18.04.2014 20:30, Bob Rossi wrote: > > > > > > The solution to these problems is pretty clear, lets give developers an API. > > > > I am not sure what's different between "API" and GDB/MI, which is also an > > API or some sort. No matter what a new API might be, the problems of GDB > > changes and supporting multiple versions of GDB will be the same, except for > > wrong grammar. Web developers have the same problems with API changes, > > for all I know. > > > > The difference is very important - in case of grammar the only way to verify that GDB > really follows it is to write and maintain complete set of test cases while in case of API > compiler will do it for you automatically. I can see that the acronym API is really an ambiguous term here. The API i'm refering to is something like, void gdbwire_set_breakpoint(char *file, int line); Asking GDB to set a breakpoint, interpreting the response. It should also be possible to recieve events, like when the breakpoint was hit. This opens the library up to dozens of possible combinations. - How does gdb respond to breakpoints for C or ada? - How does gdb respond to breakpoints in 2004 vs 2014 - What version of MI is being used? I'm being idealistic I know. When writing a front end, I really don't want to deal with these details. The way GDB is designed now, it forces me to. In fact, it forces everyone to. I'm trying to help mitigate that problem. Lets see how it goes. Bob Rossi