From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16470 invoked by alias); 16 Apr 2002 12:55:54 -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 16169 invoked from network); 16 Apr 2002 12:55:49 -0000 Received: from unknown (HELO mirapoint.inter.net.il) (192.114.186.20) by sources.redhat.com with SMTP; 16 Apr 2002 12:55:49 -0000 Received: from zaretsky (diup-217-183.inter.net.il [213.8.217.183]) by mirapoint.inter.net.il (Mirapoint Messaging Server MOS 2.9.3.2) with ESMTP id ABF25955; Tue, 16 Apr 2002 15:55:35 +0300 (IDT) Date: Tue, 16 Apr 2002 05:55:00 -0000 From: "Eli Zaretskii" To: dje@transmeta.com Message-Id: <4060-Tue16Apr2002154926+0300-eliz@is.elta.co.il> CC: gdb@sources.redhat.com In-reply-to: <15547.51222.125386.852824@casey.transmeta.com> (message from Doug Evans on Mon, 15 Apr 2002 23:43:34 -0700 (PDT)) Subject: Re: does bpstat_print stop printing prematurely? Reply-to: Eli Zaretskii References: <200204152003.NAA11126@casey.transmeta.com> <15547.51222.125386.852824@casey.transmeta.com> X-SW-Source: 2002-04/txt/msg00262.txt.bz2 > From: Doug Evans > Date: Mon, 15 Apr 2002 23:43:34 -0700 (PDT) > > Here's a session showing how to recreate it. Thanks, I reproduced the bug on my machine. However, I don't know what would it take to fix this, since I don't understand the comment in bpstat_print before the offending loop. Anybody?