From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24612 invoked by alias); 13 Mar 2005 23:38:24 -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 24600 invoked from network); 13 Mar 2005 23:38:19 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 13 Mar 2005 23:38:19 -0000 Received: from drow by nevyn.them.org with local (Exim 4.44 #1 (Debian)) id 1DAcet-0003km-RF; Sun, 13 Mar 2005 18:38:07 -0500 Date: Sun, 13 Mar 2005 23:38:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Eli Zaretskii , dave.korn@artimi.com, kostik@ispras.ru, gdb@sources.redhat.com Subject: Re: MI output command error Message-ID: <20050313233807.GA14372@nevyn.them.org> Mail-Followup-To: Nick Roberts , Eli Zaretskii , dave.korn@artimi.com, kostik@ispras.ru, gdb@sources.redhat.com References: <16946.1979.617105.196894@farnswood.snap.net.nz> <20050311213042.GA14428@nevyn.them.org> <16946.4725.343793.980977@farnswood.snap.net.nz> <01c526ed$Blat.v2.4$2b933720@zahav.net.il> <16948.2374.864364.458035@farnswood.snap.net.nz> <20050313154027.GA18342@nevyn.them.org> <16948.40725.317349.246550@farnswood.snap.net.nz> <20050313202538.GA4946@nevyn.them.org> <16948.52610.349827.789960@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16948.52610.349827.789960@farnswood.snap.net.nz> User-Agent: Mutt/1.5.6+20040907i X-SW-Source: 2005-03/txt/msg00151.txt.bz2 On Mon, Mar 14, 2005 at 12:32:18PM +1300, Nick Roberts wrote: > > > At the moment I have some time, so I can offer to try. I will need some > > > hand holding though. What files should I look at, and what behaviour > > > would you expect? > > > > Have I mentioned that I don't know anything about MI? :-) I'm afraid I > > have no advice. I would expect -exec-interrupt to send a signal to the > > target process, just like GDB's SIGINT handler does. Which isn't > > perfect, but generally works. > > OK. Theres an example in the manual that I can follow: > > (gdb) > 111-exec-continue > 111^running > > (gdb) > 222-exec-interrupt > 222^done > (gdb) > 111*stopped,signal-name="SIGINT",signal-meaning="Interrupt", > frame={addr="0x00010140",func="foo",args=[],file="try.c",line="13"} > (gdb) > > However, with it looking like Andrew has gone AWOL, who would review any such > patches? Please, let's discuss that after we have patches to review... I can review patches for technical merit, as can the other GDB maintainers, and I don't think Andrew is "AWOL". Maintainers are allowed to have lives of their own, you know :-) I'm sure he will be active again soon, or if (unlikely) not, we can seek new MI maintainers once we find out where he went. -- Daniel Jacobowitz CodeSourcery, LLC