From: Daniel Jacobowitz <drow@false.org>
To: "Frédéric Riss" <frederic.riss@gmail.com>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Prints the frame id when target stops
Date: Wed, 17 Jan 2007 22:17:00 -0000 [thread overview]
Message-ID: <20070117221742.GA15116@nevyn.them.org> (raw)
In-Reply-To: <1169071153.5155.71.camel@funkylaptop>
On Wed, Jan 17, 2007 at 10:59:13PM +0100, Frédéric Riss wrote:
> Have you an idea how you would like the caching to work? Do you mean not
> discarding the frame cache, or caching the returned string?
How much do we know about why it takes a long time?
For instance:
- We can speed up the psymtab lookup which currently shows up in
profiles. A coworker of mine gave me some clever ideas on how
to do this if anyone wants to try it :-)
- We can speed up prologue analyzers by judicious use of caching,
in a way that's completely reliable. DWARF2 CFI is already pretty
speedy.
If these sorts of things are enough to help...
> Also, I don't see how we could have better checks within GDB than within
> the frontend. The only reliable check is IMHO to compare frame ids after
> steps and nexts.
I suspect you can only do this in stepi, really - step/next can end up
in strange places...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-17 22:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 16:21 Denis PILAT
2007-01-15 21:37 ` Nick Roberts
2007-01-15 23:11 ` Nick Roberts
2007-01-15 23:49 ` Nick Roberts
2007-01-17 8:26 ` Denis PILAT
2007-01-16 16:20 ` Vladimir Prus
2007-01-16 21:12 ` Nick Roberts
2007-01-16 23:38 ` Vladimir Prus
2007-01-17 6:18 ` Daniel Jacobowitz
2007-01-17 21:46 ` Vladimir Prus
2007-01-20 17:02 ` Daniel Jacobowitz
2007-01-17 21:29 ` Mark Kettenis
2007-01-17 21:38 ` Vladimir Prus
2007-01-17 21:59 ` Frédéric Riss
2007-01-17 22:14 ` Vladimir Prus
2007-01-18 8:00 ` Frederic RISS
2007-01-17 22:17 ` Daniel Jacobowitz [this message]
2007-01-18 7:58 ` Frederic RISS
2007-01-18 18:34 ` Jim Blandy
2007-01-19 14:28 ` Denis PILAT
2007-01-20 17:00 ` Daniel Jacobowitz
2007-01-18 19:59 ` Daniel Jacobowitz
2007-01-17 6:19 ` Daniel Jacobowitz
2007-01-18 21:13 ` Nick Roberts
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=20070117221742.GA15116@nevyn.them.org \
--to=drow@false.org \
--cc=frederic.riss@gmail.com \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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