From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26069 invoked by alias); 11 Jul 2002 22:55:12 -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 26062 invoked from network); 11 Jul 2002 22:55:11 -0000 Received: from unknown (HELO corb.mc.mpls.visi.com) (208.42.156.1) by sources.redhat.com with SMTP; 11 Jul 2002 22:55:11 -0000 Received: from grante.comtrol.com (isis.visi.com [209.98.98.8]) by corb.mc.mpls.visi.com (Postfix) with SMTP id 65B22817F for ; Thu, 11 Jul 2002 17:55:11 -0500 (CDT) Received: (qmail 30105 invoked by uid 500); 11 Jul 2002 22:58:56 -0000 Date: Thu, 11 Jul 2002 15:55:00 -0000 From: Grant Edwards To: gdb@sources.redhat.com Subject: RDI code busy-waiting on running target? Message-ID: <20020711175854.A29971@visi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-SW-Source: 2002-07/txt/msg00119.txt.bz2 [gdb 5.1.1, rdi target] I've noticed that gdb uses all the CPU it can get while the target is running (e.g. busy-waiting 'till target stops). I'm building 5.2 to see if it still does that, but the build is taking forever since I'm also testing some ARM code and gdb 5.1.1 is using 50% of the CPU waiting for the target to stop. :) Anybody else seen this? -- Grant Edwards grante@visi.com