From: Daniel Jacobowitz <drow@false.org>
To: jagorak <jagorak@wp.pl>
Cc: gdb@sourceware.org
Subject: Re: Setting a variable is very slow.
Date: Sat, 21 Apr 2007 13:41:00 -0000 [thread overview]
Message-ID: <20070421134117.GA10446@caradoc.them.org> (raw)
In-Reply-To: <1546343093.20070421134325@wp.pl>
On Sat, Apr 21, 2007 at 01:43:25PM +0100, jagorak wrote:
> I need to make hundreds of such assignments & calls. The problem is -
> setting a single variable is very slow (in most cases it takes much
> more time to set a single variable than to call a procedure, even if
> the procedure is not very simple).
>
> Any ideas why this is the case?
I know of some problems in this area, but it's not clear which one is
your problem here. Could you try building gdb with
--enable-profiling? It should generate a gmon.out. That might not
show the real problem; if you want to just build a debuggable version
and use oprofile, that might work better. It depends whether GDB is
eating CPU or being wasteful with ptrace operations.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-21 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 12:43 jagorak
2007-04-21 12:50 ` Robert Dewar
2007-04-21 13:41 ` Daniel Jacobowitz [this message]
2007-04-30 20:05 ` Re[2]: " jagorak
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=20070421134117.GA10446@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jagorak@wp.pl \
/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