From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23965 invoked by alias); 11 Mar 2005 21:05:23 -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 23810 invoked from network); 11 Mar 2005 21:05:16 -0000 Received: from unknown (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org with SMTP; 11 Mar 2005 21:05:16 -0000 Received: from farnswood.snap.net.nz (p22-tnt1.snap.net.nz [202.124.110.22]) by viper.snap.net.nz (Postfix) with ESMTP id 3575448FD18; Sat, 12 Mar 2005 10:05:15 +1300 (NZDT) Received: by farnswood.snap.net.nz (Postfix, from userid 501) id 66FF762FBE; Fri, 11 Mar 2005 21:03:57 +0000 (GMT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16946.1979.617105.196894@farnswood.snap.net.nz> Date: Fri, 11 Mar 2005 21:05:00 -0000 To: Daniel Jacobowitz Cc: Dave Korn , Karganov Konstantin , GDB Subject: Re: MI output command error X-SW-Source: 2005-03/txt/msg00125.txt.bz2 > I'm as mystified as Dave as to how you could read the manual and > believe GDB/MI was designed to operate synchronously. A number of MI > commands have documentation that begins with "Asynchronous command." In > particular, look at -exec-interrupt, which makes no sense as a > synchronous command. I think the problem that people like Bob and myself have with this, is that when GDB is compiled out of the box, it doesn't operate asynchronously. So if we run GDB using MI, -exec-interrupt *doesn't* interrupt the inferior: ... ^done (gdb) 111-exec-continue 111^running (gdb) 222-exec-interrupt Dave Korn's explanation is very helpful. Considering the MI output to be asynchronous, makes it much easier to understand. The fact remains, however, that for native targets at least (the most common configuration?), operation is synchronous. It leads me to wonder how this discrepancy arises. Nick