From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: cgd@broadcom.com, gdb@sources.redhat.com
Subject: Re: Next for GDB
Date: Tue, 05 Aug 2003 04:16:00 -0000 [thread overview]
Message-ID: <20030805041640.GA13510@nevyn.them.org> (raw)
In-Reply-To: <3F2F2E85.8070805@redhat.com>
On Tue, Aug 05, 2003 at 12:11:49AM -0400, Andrew Cagney wrote:
> Also `making a dead cat bounce'. Layering a simulator over the top of
> another target so the simulator uses the target for registers and
> memory. Would make possible:
> - less intrusive inferior function calls (don't write the results back)
> - executing code on dead targets
> - simulated single stepping
> this would involve a lot more work so ...
That has got to be one of the neatest ideas I've heard in a long
time...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-05 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 23:46 Andrew Cagney
[not found] ` <mailpost.1059781632.20888@news-sj1-1>
2003-08-02 1:37 ` cgd
2003-08-05 4:11 ` Andrew Cagney
2003-08-05 4:16 ` Daniel Jacobowitz [this message]
2003-08-02 0:54 Michael Elizabeth Chastain
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=20030805041640.GA13510@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=cgd@broadcom.com \
--cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).