From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20193 invoked by alias); 19 Sep 2005 13:17:57 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19903 invoked by uid 22791); 19 Sep 2005 13:17:46 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 19 Sep 2005 13:17:46 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1EHLWh-0004bj-Us; Mon, 19 Sep 2005 09:17:44 -0400 Date: Mon, 19 Sep 2005 13:17:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: gdb-patches@sources.redhat.com Subject: Re: RFC: MI output during program execution Message-ID: <20050919131743.GA17264@nevyn.them.org> Mail-Followup-To: Nick Roberts , gdb-patches@sources.redhat.com References: <17142.56731.941946.838268@farnswood.snap.net.nz> <20050808130516.GA9046@nevyn.them.org> <17160.63891.324530.937796@farnswood.snap.net.nz> <430B9BF8.500@apple.com> <17188.60739.749026.738477@farnswood.snap.net.nz> <17198.37622.443418.520082@farnswood.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17198.37622.443418.520082@farnswood.snap.net.nz> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-09/txt/msg00168.txt.bz2 On Mon, Sep 19, 2005 at 10:29:10PM +1200, Nick Roberts wrote: Content-Description: message body text > > I've started a merge on current CVS (for some reason gdb-413 seemed to > > include everything except the GDB source). Getting MI output during > > program execution seems to be closely related to making GDB asynchronous. > > I couldn't attempt such a task on my own but, using the Apple code as a > > prototype, it doesn't look too difficult. When I have something working > > perhaps I could put it on a branch. > > I now have something that works for GNU/Linux (probably under limited > conditions). With MI it now picks up mi_exec_async_cli_cmd_continuation to > print the *stopped record, even with CLI commands like "run": Great! > I attach the new files and a set of diffs against HEAD from about 20:00 NZST > (+12 GMT) Sept 19 2005, for anyone who might like to test the functionality. > If I am given approval to commit these changes to a branch then I will create > ChangeLog entries (attributed to Apple). > > I presume there is more freedom to committing on a non-release branch. What > are the rules? The rules for a branch are, generally, up to the branch owner. The only one I'll insist on is that copyright assignments be handled in the same way as for HEAD, which is not a problem here. See: http://sources.redhat.com/gdb/current/onlinedocs/gdbint_15.html#SEC133 (which are mostly guidelines rather than rules). So, you can create a branch if you'd like. I took a quick look at the changes, but couldn't make heads or tails out of what was going on. Also, I think the diff is corrupted; the changes to linux-nat.c cut off in a very strange place in child_wait(). Maybe when it's been cleaned up a little we can look for a way to do this that doesn't involve pthreads. -- Daniel Jacobowitz CodeSourcery, LLC