From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19308 invoked by alias); 26 Apr 2002 15:21:59 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 19237 invoked from network); 26 Apr 2002 15:21:55 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 26 Apr 2002 15:21:55 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C55BC3D5A; Fri, 26 Apr 2002 11:21:54 -0400 (EDT) Message-ID: <3CC97092.1000708@cygnus.com> Date: Fri, 26 Apr 2002 08:21:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.9) Gecko/20020424 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jim Ingham Cc: Eli Zaretskii , gdb@sources.redhat.com Subject: Re: Questions about GDB-MI Interface` References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00463.txt.bz2 > > Yes, this is the way that we do it. After all, the intepreter-exec command > is an MI command, so I just accumulate the hook results in the result of the > MI command, and send them all when it is done. This works great in the > async case, because even if you start the inferior you get an immediate > "done" for the command, with all the hook results as well. I think this > will have to be worked on a bit in the synchronous case, so that you send > some out-of-band MI message. Though it has a few of its own problems, the > Async stuff makes this sort of thing MUCH easier!! Another, er, one of those, er, ``overriding objectives'' is ment to be converting all natives to async mode. I'm not exactly following this one through with much vigor though (I'm having too much fun just keeping multi-arch at bay :-). However, the positive is that we've now got native async code to refer to. enjoy, Andrew