From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3127 invoked by alias); 18 Aug 2009 15:42:34 -0000 Received: (qmail 3114 invoked by uid 22791); 18 Aug 2009 15:42:33 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 18 Aug 2009 15:42:28 +0000 Received: from zps19.corp.google.com (zps19.corp.google.com [172.25.146.19]) by smtp-out.google.com with ESMTP id n7IFgOIt020457 for ; Tue, 18 Aug 2009 16:42:25 +0100 Received: from rv-out-0708.google.com (rvfb17.prod.google.com [10.140.179.17]) by zps19.corp.google.com with ESMTP id n7IFgL7u021175 for ; Tue, 18 Aug 2009 08:42:22 -0700 Received: by rv-out-0708.google.com with SMTP id b17so1429845rvf.30 for ; Tue, 18 Aug 2009 08:42:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.162.20 with SMTP id k20mr2783150rve.255.1250610141607; Tue, 18 Aug 2009 08:42:21 -0700 (PDT) In-Reply-To: <4A8A95E0.7090409@Sun.COM> References: <8ac60eac0908140922m57367e9dn464783d8ff625474@mail.gmail.com> <4A8A95E0.7090409@Sun.COM> Date: Tue, 18 Aug 2009 16:17:00 -0000 Message-ID: <8ac60eac0908180842q296b902fh38d01b89dcf54af3@mail.gmail.com> Subject: Re: [patch] Fix Darwin breakage From: Paul Pluzhnikov To: Christian Thalinger Cc: gdb-patches ml Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true 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: 2009-08/txt/msg00278.txt.bz2 On Tue, Aug 18, 2009 at 4:52 AM, Christian Thalinger wrote: > I tried that patch and it kind of works. =A0But running a program takes > ages (about 5-10 minutes), with GDB using 100% CPU time. Could you attach another instance of GDB to the one that consumes 100% CPU and see where the CPU-bound GDB is? (Or use dtrace to get ustack histogram :-) > The backtrace looks fine, but arguments and local variables are not > visible. =A0Loaded shared libraries look OK: Steps to reproduce? Could you make a tar of /Users/twisti/bsd-port/hotspot/build/ available? Thanks, --=20 Paul Pluzhnikov