Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
	Jan Kratochvil <jan.kratochvil@redhat.com>,
	       Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH] On-demand loading of shlib's debuginfo
Date: Thu, 21 Jul 2011 20:38:00 -0000	[thread overview]
Message-ID: <m3bown1isk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201107211503.41130.pedro@codesourcery.com> (Pedro Alves's	message of "Thu, 21 Jul 2011 15:03:40 +0100")

>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

Pedro> I was under the impression that the debug info loading would be
Pedro> the major hog, and lazying that alone would stand on its own (as
Pedro> this patch, but with a solib_contains_address_pc_p call in
Pedro> solib_on_demand_load instead of the new match_pc_solist stuff).

There's also this, which I still haven't checked in:

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

This defers reading debuginfo for new inferiors until some event happens
that requires it.

It turns out that Gary's recent patches will (most likely -- I didn't
try it yet) fix the problem pointed out in that message.

Anyway, this approach does help quite a bit.

Tom


  reply	other threads:[~2011-07-21 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19  5:34 Sergio Durigan Junior
2011-07-20 22:01 ` Jan Kratochvil
2011-07-21 11:13   ` Pedro Alves
2011-07-21 14:03     ` Jan Kratochvil
2011-07-21 15:19       ` Pedro Alves
2011-07-21 20:38         ` Tom Tromey [this message]
2011-07-21 18:43     ` Sergio Durigan Junior
2011-07-21 19:21       ` Pedro Alves
2011-07-21 20:10         ` Jan Kratochvil

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=m3bown1isk.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pedro@codesourcery.com \
    --cc=sergiodj@redhat.com \
    /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