This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Fix Darwin breakage

From: Paul Pluzhnikov <ppluzhnikov at google dot com>
To: Christian Thalinger <Christian dot Thalinger at sun dot com>
Cc: gdb-patches ml <gdb-patches at sourceware dot org>
Date: Tue, 18 Aug 2009 08:42:21 -0700
Subject: Re: [patch] Fix Darwin breakage
References: <8ac60eac0908140922m57367e9dn464783d8ff625474@mail.gmail.com> <4A8A95E0.7090409@Sun.COM>

On Tue, Aug 18, 2009 at 4:52 AM, Christian
Thalinger<Christian.Thalinger@sun.com> wrote:

> I tried that patch and it kind of works. ?But 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. ?Loaded shared libraries look OK:

Steps to reproduce?
Could you make a tar of /Users/twisti/bsd-port/hotspot/build/ available?

Thanks,
-- 
Paul Pluzhnikov

Follow-Ups:
- Re: [patch] Fix Darwin breakage
  - From: Christian Thalinger

References:
- [patch] Fix Darwin breakage
  - From: Paul Pluzhnikov
- Re: [patch] Fix Darwin breakage
  - From: Christian Thalinger

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]