From: 'Daniel Jacobowitz' <drow@false.org>
To: Eric Weddington <eweddington@cso.atmel.com>
Cc: 'Jim Blandy' <jimb@codesourcery.com>, gdb@sourceware.org
Subject: Re: What should a CPU simulator support?
Date: Fri, 06 Jul 2007 22:13:00 -0000 [thread overview]
Message-ID: <20070706221321.GA7338@caradoc.them.org> (raw)
In-Reply-To: <027201c7c018$0b14a940$10745f0a@cso.atmel.com>
On Fri, Jul 06, 2007 at 03:53:10PM -0600, Eric Weddington wrote:
> For the AVR target, there is no internal simulator in GDB, but there is an
> external simulator available, simulavr:
> <https://savannah.nongnu.org/projects/simulavr>
> which uses the GDB remote protocol.
>
> You specifically recommend that we keep this layout (external simultor),
> rather than try to develop a new AVR simulator that would go into the GDB
> tree, correct?
Yes, I do. That doesn't mean GDB can't change to work better with
your simulator, of course - or that using a built-in simulator is
somehow wrong. But I've found that a strict partition between a
cooperating simulator and a cooperating GDB has the best results.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-06 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 2:30 Wenbo Yang
2007-07-05 19:14 ` Jim Blandy
[not found] ` <c9d32f760707051300r192ea70bj3edcfc00892c5714@mail.gmail.com>
2007-07-05 21:32 ` Jim Blandy
2007-07-06 10:27 ` Robert Norton
2007-07-06 12:02 ` Daniel Jacobowitz
2007-07-06 12:10 ` Robert Norton
2007-07-06 12:20 ` Daniel Jacobowitz
2007-07-06 21:56 ` Eric Weddington
2007-07-06 22:13 ` 'Daniel Jacobowitz' [this message]
[not found] <c9d32f760707031824u7836642aud35629ae88fbfe3@mail.gmail.com>
2007-07-04 1:26 ` s88
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=20070706221321.GA7338@caradoc.them.org \
--to=drow@false.org \
--cc=eweddington@cso.atmel.com \
--cc=gdb@sourceware.org \
--cc=jimb@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