From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26532 invoked by alias); 20 Mar 2008 01:58:14 -0000 Received: (qmail 26393 invoked by uid 22791); 20 Mar 2008 01:58:13 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 20 Mar 2008 01:57:40 +0000 Received: from kahikatea.snap.net.nz (115.62.255.123.dynamic.snap.net.nz [123.255.62.115]) by viper.snap.net.nz (Postfix) with ESMTP id 4B9D83DA3EC; Thu, 20 Mar 2008 14:57:38 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 86EFA8FC6D; Thu, 20 Mar 2008 13:57:32 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18401.50314.796016.448704@kahikatea.snap.net.nz> Date: Thu, 20 Mar 2008 01:58:00 -0000 To: Pedro Alves Cc: luisgpm@linux.vnet.ibm.com, gdb-patches@sourceware.org Subject: Re: linux native async mode support In-Reply-To: <200803192318.45355.pedro@codesourcery.com> References: <200803140810.22883.pedro@codesourcery.com> <18400.36720.580645.362838@kahikatea.snap.net.nz> <1205943875.32489.10.camel@gargoyle.br.ibm.com> <200803192318.45355.pedro@codesourcery.com> X-Mailer: VM 7.19 under Emacs 22.1.92.2 X-IsSubscribed: yes 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: 2008-03/txt/msg00295.txt.bz2 > It's really a timing issue, and that's why I can't reproduce -- it is > timing/host sensitive. So this means this problem isn't related to my > patch, but it's a general async issue, that may be visible too in "target > async" connected to a gdbserver for example. Although since we're running > over a slower link there, nobody was probably seeing it. I don't know > enough MI to say if this is according to the spec or not, but it feels like > a testsuite deficiency, is it not? I don't think it's a testsuite deficiency but, coincidentally, Vladimir has just been talking about removing the "(gdb) \n" after ^running. This may be a good reason to do it. The patch below fixes the fails that I was seeing in mi-var-child-f.exp. -- Nick http://www.inet.net.nz/~nickrob *** inf-loop.c 15 Mar 2008 22:34:07 +1300 1.11 --- inf-loop.c 20 Mar 2008 13:55:12 +1200 *************** inferior_event_handler (enum inferior_ev *** 91,98 **** was_sync = sync_execution; async_enable_stdin (); - do_all_continuations (); - if (current_language != expected_language) { if (language_mode == language_mode_auto) --- 91,96 ---- *************** inferior_event_handler (enum inferior_ev *** 101,106 **** --- 99,106 ---- } } + do_all_continuations (); + /* If the continuation did not start the target again, prepare for interation with the user. */ if (!target_executing)