Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Improve performance with lots of shared libraries
Date: Fri, 01 Jul 2011 17:19:00 -0000	[thread overview]
Message-ID: <m3liwhapgl.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110701165109.GA3399@redhat.com> (Gary Benson's message of	"Fri, 1 Jul 2011 17:51:09 +0100")

>>>>> "Gary" == Gary Benson <gbenson@redhat.com> writes:

Gary> While working on a new linker-debugger interface I took some time out
Gary> to do a bit of profiling to see exactly where gdb is spending its time
Gary> with inferiors that load a lot of shared libraries, and it turned out
Gary> that the top 30% of the profile was update_section_map and the things
Gary> it calls.

Nice.

I think this will solve a problem I had:

    http://sourceware.org/ml/gdb-patches/2011-03/msg00606.html

I haven't committed that yet, but I will, sooner or later.

Gary> I'd really appreciate feedback from people who know this part of gdb
Gary> well, as well as feedback from those users who are using gdb on
Gary> many-solibs applications as to whether this patch helps.

I think Pedro is the person to review it.  The idea seems sound to me,
but as you note, this code is very dense.

I have a couple nits.

Gary> +/* Nonzero if the location stopoed at is the shlib event breakpoint.  */

Typo, "stopped".

Gary> +static int
Gary> +at_solib_event_breakpoint (struct execution_control_state *ecs)
Gary> +{
Gary> +  struct solib_event_breakpoint_helper_arg arg;
Gary> +  arg.prev_pc = ecs->event_thread->prev_pc;

Blank line between declarations and code.

Tom


  reply	other threads:[~2011-07-01 17:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-01 16:51 Gary Benson
2011-07-01 17:19 ` Tom Tromey [this message]
2011-07-04 14:10   ` Gary Benson
2011-07-01 17:32 ` Joel Brobecker
2011-07-04 14:21   ` Gary Benson
2011-07-01 17:45 ` Pedro Alves
2011-07-01 17:57   ` Pedro Alves
2011-09-09 14:25 Gary Benson
2011-09-09 14:35 ` Daniel Jacobowitz
2011-09-09 14:51   ` Jan Kratochvil
2011-09-09 15:04     ` Pedro Alves
2011-09-09 19:41       ` Jan Kratochvil
2011-09-12 12:44         ` Pedro Alves
2011-09-12 16:44           ` Jan Kratochvil
2011-09-14  9:28             ` Gary Benson
2011-10-04 19:46               ` Tom Tromey
2011-09-09 15:11     ` Pedro Alves
2011-09-09 14:53 ` Jan Kratochvil
2011-10-04 20:03   ` Tom Tromey
2011-09-22 17:35 Gary Benson

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=m3liwhapgl.fsf@fleche.redhat.com \
    --to=tromey@redhat.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