From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19486 invoked by alias); 21 Mar 2008 15:47:56 -0000 Received: (qmail 19471 invoked by uid 22791); 21 Mar 2008 15:47:56 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 21 Mar 2008 15:47:36 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id E8BBA98298; Fri, 21 Mar 2008 15:47:34 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id C904B98278; Fri, 21 Mar 2008 15:47:34 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JcjSw-0007Pc-2S; Fri, 21 Mar 2008 11:47:34 -0400 Date: Fri, 21 Mar 2008 15:47:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Pedro Alves , luisgpm@linux.vnet.ibm.com, gdb-patches@sourceware.org Subject: Re: linux native async mode support Message-ID: <20080321154734.GL25307@caradoc.them.org> Mail-Followup-To: Nick Roberts , Pedro Alves , luisgpm@linux.vnet.ibm.com, gdb-patches@sourceware.org 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> <18401.50314.796016.448704@kahikatea.snap.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18401.50314.796016.448704@kahikatea.snap.net.nz> User-Agent: Mutt/1.5.17 (2007-12-11) 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/msg00310.txt.bz2 On Thu, Mar 20, 2008 at 01:57:30PM +1200, Nick Roberts wrote: > > 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. This seems to be a general async issue, not related specifically to Linux. So let's address it separately. If you think this patch is right, could you post it in a new thread with an explanation, please? -- Daniel Jacobowitz CodeSourcery