This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: What should a CPU simulator support?

From: 'Daniel Jacobowitz' <drow at false dot org>
To: Eric Weddington <eweddington at cso dot atmel dot com>
Cc: 'Jim Blandy' <jimb at codesourcery dot com>, gdb at sourceware dot org
Date: Fri, 6 Jul 2007 18:13:21 -0400
Subject: Re: What should a CPU simulator support?
References: <20070706122023.GA11676@caradoc.them.org> <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

References:
- Re: What should a CPU simulator support?
  - From: Daniel Jacobowitz
- RE: What should a CPU simulator support?
  - From: Eric Weddington

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]