From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eager@eagercon.com
Cc: eager@eagercon.com, gdb@sources.redhat.com, vladimir@codesourcery.com
Subject: Re: frame cache
Date: Tue, 24 Jul 2007 18:45:00 -0000 [thread overview]
Message-ID: <200707241832.l6OIWAUp018805@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <46A6387F.8020303@eagercon.com> (message from Michael Eager on Tue, 24 Jul 2007 10:35:59 -0700)
> Date: Tue, 24 Jul 2007 10:35:59 -0700
> From: Michael Eager <eager@eagercon.com>
>
> When I put debugging code in <target>_analyze_prologue(), I see
> that it is called over and over while executing a "next" command.
> All those bits going back and forth over the serial line to the
> target.
If that's the case, there's something wrong; prologue analysis should
only be done as a last resort, i.e. when proper debug information is
not available.
Your effort might be better spent on determining why proper debug info
is not present instead of optimizing <target>_analyze_prologue().
next prev parent reply other threads:[~2007-07-24 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 17:08 Michael Eager
2007-07-24 17:14 ` Michael Eager
2007-07-24 17:36 ` Daniel Jacobowitz
2007-07-24 18:19 ` Michael Eager
2007-07-24 18:34 ` Daniel Jacobowitz
2007-07-24 18:34 ` Mark Kettenis
2007-07-24 17:17 ` Daniel Jacobowitz
2007-07-24 18:10 ` Michael Eager
2007-07-24 18:22 ` Daniel Jacobowitz
2007-07-24 18:45 ` Michael Eager
2007-07-24 18:45 ` Mark Kettenis [this message]
2007-07-24 19:08 ` Michael Eager
2007-07-25 2:18 ` Paul Koning
2007-07-27 9:18 ` Wenbo Yang
2007-07-30 22:01 ` Michael Eager
2007-07-30 23:07 ` Mark Kettenis
2007-07-31 3:51 ` Wenbo Yang
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=200707241832.l6OIWAUp018805@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eager@eagercon.com \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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