From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Klee Dienes <kdienes@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Cached function lookup
Date: Wed, 06 Feb 2002 10:58:00 -0000 [thread overview]
Message-ID: <npsn8emo5c.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <8A9ABA76-1A1B-11D6-BA6D-0030653FA4C6@apple.com>
Klee Dienes <kdienes@apple.com> writes:
> (This is basically the same patch I sent last week, just updated
> to the latest source base.)
>
> This patch allows functions in the target used by GDB ("malloc",
> "scm_lookup_cstr", and later a ton of Objective-C functions) to have
> their values cached and re-used unless the symbol table has changed
> in-between calls. This is a performance win overall, and a particular
> win when dispatching Objective-C method calls and looking up
> Objective-C type information from the runtime.
>
> 2002-02-04 Klee Dienes <kdienes@apple.com>
>
> * breakpoint.c (breakpoint_re_set, breakpoint_re_set_all,
> breakpoint_update): Instead of re-parsing all deferred
> breakpoints
> every time breakpoint_re_set is called, increment a generation
> number. When breakpoints need to be up-to-date, call
> breakpoint_update. This prevents unnecessary re-parsing of
> breakpoint information (and massive future-break spam) when
> multiple shared libraries are loaded at the same time.
Let me see if I understand the situation:
The inferior hits a shlib event breakpoint, indicating that it's
loaded or unloaded some stuff. GDB scans the dynamic linker's table,
and discovers that several new shared libraries have been loaded.
As the code currently stands, GDB will recompute its breakpoints'
addresses after each solib's symbols are read. Your change makes GDB
delay this until it's about to insert the breakpoints.
Is that correct?
next prev parent reply other threads:[~2002-02-06 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 1:34 Klee Dienes
2002-02-06 10:58 ` Jim Blandy [this message]
2002-02-28 7:22 ` Andrew Cagney
2002-03-09 21:42 ` Andrew Cagney
2002-03-09 21:54 ` Andrew Cagney
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=npsn8emo5c.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kdienes@apple.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