Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Christian Thalinger <Christian.Thalinger@sun.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [patch] Fix Darwin breakage
Date: Tue, 18 Aug 2009 16:17:00 -0000	[thread overview]
Message-ID: <8ac60eac0908180842q296b902fh38d01b89dcf54af3@mail.gmail.com> (raw)
In-Reply-To: <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


  reply	other threads:[~2009-08-18 15:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 16:32 Paul Pluzhnikov
2009-08-14 17:56 ` Paul Pluzhnikov
2009-08-14 19:09   ` Tom Tromey
2009-08-14 18:32 ` Tom Tromey
2009-08-14 19:15   ` Paul Pluzhnikov
2009-08-18 12:24 ` Christian Thalinger
2009-08-18 16:17   ` Paul Pluzhnikov [this message]
2009-08-20 17:01     ` Christian Thalinger
2009-08-20 17:09       ` Paul Pluzhnikov
2009-08-20 17:16         ` Christian Thalinger
2009-08-21 11:30         ` Christian Thalinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ac60eac0908180842q296b902fh38d01b89dcf54af3@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=Christian.Thalinger@sun.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox