From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30499 invoked by alias); 7 Feb 2003 06:22:49 -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 30488 invoked from network); 7 Feb 2003 06:22:49 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 172.16.49.205 with SMTP; 7 Feb 2003 06:22:49 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id h176Mln07953; Fri, 7 Feb 2003 00:22:47 -0600 Date: Fri, 07 Feb 2003 06:22:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200302070622.h176Mln07953@duracef.shout.net> To: carlton@math.stanford.edu, gdb@sources.redhat.com Subject: Re: gdb.c++/annota2.exp: annotate-quit X-SW-Source: 2003-02/txt/msg00143.txt.bz2 dc> Is anybody else seeing this? dc> Does anybody currently see it KFAIL? I'll run it a couple of hundred times in the morning and report back. dc> Is there any chance that the interpreter patch from yesterday dc> or today might have fixed this bug? Yes. The test case reads a prompt from gdb, sends a ^C to gdb, and expects gdb to react to it. I suspect there's a race condition involving job control so that the incoming ^C races with the operating system enabling gdb to receive signals (as opposed to the inferior receiving the signal). So something that touches the main prompt/read loop could touch this. (I admit I'm guessing a lot here). Michael C