RE: What should a CPU simulator support?

["Robert Norton" <rnorton@broadcom.com>]

> -----Original Message-----
> From: gdb-owner@sourceware.org 
> [mailto:gdb-owner@sourceware.org] On Behalf Of Jim Blandy
> Sent: 05 July 2007 22:32
> To: s88
> Cc: Wenbo Yang; gdb@sourceware.org
> Subject: Re: What should a CPU simulator support?
> <snip>
> There are two ways for GDB to connect to a simulator:
> 
> - You can make the simulator into a '.a' library, have it implement
>   the interface in include/gdb/remote-sim.h, and link it directly with
>   GDB.  Then the GDB 'target sim' command will initialize the
>   simulator, and subsequent 'run', 'continue', 'step' (etc.) commands
>   will apply to it.
> 
>   This is simplest for the end user: no separate program to start up,
>   no separate program file to find, and so on.

Is this still the recommended way of making a built-in simulator? I
noticed when upgrading our port that the api for simulator implemented
breakpoints has been removed! We're not interested in implementing soft
breakpoints so I had to resurrect this support in remote-sim.c.

Cheers,

Robert