From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20112 invoked by alias); 26 Nov 2002 14:48:27 -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 20099 invoked from network); 26 Nov 2002 14:48:25 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 26 Nov 2002 14:48:25 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 0A25C3F30; Tue, 26 Nov 2002 09:48:20 -0500 (EST) Message-ID: <3DE389B3.9060904@redhat.com> Date: Tue, 26 Nov 2002 06:48:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Cagney Cc: gdb@sources.redhat.com Subject: Re: [Fwd: Re: gdb/725: Crash using debug target and regcaches (in 5.3 branch?)] References: <3DDD6150.10407@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-11/txt/msg00367.txt.bz2 > FYI, > > Too many memory reads/writes was one reason for a ptrace'd threaded shlib program running slow, I suspect this is the other. To correct this. This should be a reason why GDB runs slow on GNU/Linux, but, isn't! Per other thread, this inefficiency (a few 1 000 stray ptrace calls() is trivialized by the millions (yes >1 000 000) memory read ptrace calls. GDB was probably executing more memory ptrace() calls than the target program executes instructions .... (yea, right :-). Andrew