From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20190 invoked by alias); 16 Sep 2009 20:43:02 -0000 Received: (qmail 20182 invoked by uid 22791); 16 Sep 2009 20:43:02 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 16 Sep 2009 20:42:58 +0000 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8GKgsPX015977; Wed, 16 Sep 2009 16:42:54 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n8GKgrkh026195; Wed, 16 Sep 2009 16:42:53 -0400 Received: from opsy.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n8GKgqAU011820; Wed, 16 Sep 2009 16:42:52 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 9A4E137819C; Wed, 16 Sep 2009 14:42:51 -0600 (MDT) From: Tom Tromey To: Marc Khouzam Cc: "gdb-patches\@sourceware.org" Subject: Re: Another proposal for frontends and queries. References: Reply-To: tromey@redhat.com Date: Wed, 16 Sep 2009 20:43:00 -0000 In-Reply-To: (Marc Khouzam's message of "Sun, 13 Sep 2009 22:37:48 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 X-SW-Source: 2009-09/txt/msg00532.txt.bz2 >>>>> "Marc" == Marc Khouzam writes: Marc> Proposals: [...] One idea from the user 'heinz' (sorry, I don't know your real name!) was to have a query in MI mode throw a specific error, then let the front end reissue the command with the correct response. This seems like it could be done without much difficulty. We would need a way to stuff answers into some queue that "query" reads. Maybe we would need a way to label queries (so that a new response will only be given to a specific query) -- but this could be just some machine generated thing sent along with the error. This struck me as a rather good idea: it is simple to understand and implement, and doesn't seem to have the issues associated with some other possible approaches to supporting queries (e.g., reentrant event loops). I assume I must be missing something ;-) Tom