Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* How to map memory for SH simulator?
@ 2002-01-17 10:10 William A. Gatliff
  2002-01-17 11:50 ` Frank Ch. Eigler
  0 siblings, 1 reply; 4+ messages in thread
From: William A. Gatliff @ 2002-01-17 10:10 UTC (permalink / raw)
  To: gdb

Guys:


I've seen the commands used to control the memory map for the powerpc
instruction set simulator:

http://sources.redhat.com/ml/gdb/2001-11/msg00137.html

I need to do the same thing for SH, but it doesn't look like the SH
simulator takes the same commands.  Where can I find the list of
commands supported by the SH instruction set simulator?


Thanks!


b.g.
-- 
Bill Gatliff
bgat@billgatliff.com


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to map memory for SH simulator?
  2002-01-17 10:10 How to map memory for SH simulator? William A. Gatliff
@ 2002-01-17 11:50 ` Frank Ch. Eigler
  2002-01-17 12:14   ` Andrew Cagney
  0 siblings, 1 reply; 4+ messages in thread
From: Frank Ch. Eigler @ 2002-01-17 11:50 UTC (permalink / raw)
  To: bgat; +Cc: gdb


"William A. Gatliff" <bgat@saturn.billgatliff.com> writes:

> [...]  I need to do the same thing for SH, but it doesn't look like
> the SH simulator takes the same commands.  Where can I find the list
> of commands supported by the SH instruction set simulator?

The sim/common family of simulators (sh, etc.) uses an alternate
syntax to specify additional simulated memory regions.  See the
"memory-region" option as listed in "% sh-elf-run --help" or 
"(gdb) target sim ... sim help":

- FChE


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to map memory for SH simulator?
  2002-01-17 11:50 ` Frank Ch. Eigler
@ 2002-01-17 12:14   ` Andrew Cagney
  2002-01-17 13:50     ` Frank Ch. Eigler
  0 siblings, 1 reply; 4+ messages in thread
From: Andrew Cagney @ 2002-01-17 12:14 UTC (permalink / raw)
  To: Frank Ch. Eigler; +Cc: bgat, gdb

> "William A. Gatliff" <bgat@saturn.billgatliff.com> writes:
> 
> 
>> [...]  I need to do the same thing for SH, but it doesn't look like
>> the SH simulator takes the same commands.  Where can I find the list
>> of commands supported by the SH instruction set simulator?
> 
> 
> The sim/common family of simulators (sh, etc.) uses an alternate
> syntax to specify additional simulated memory regions.  See the
> "memory-region" option as listed in "% sh-elf-run --help" or 
> "(gdb) target sim ... sim help":


Er, are you sure about this?

Andrew


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: How to map memory for SH simulator?
  2002-01-17 12:14   ` Andrew Cagney
@ 2002-01-17 13:50     ` Frank Ch. Eigler
  0 siblings, 0 replies; 4+ messages in thread
From: Frank Ch. Eigler @ 2002-01-17 13:50 UTC (permalink / raw)
  To: bgat, gdb


cagney wrote:

> [...]
> > The sim/common family of simulators (sh, etc.) uses an alternate
> > syntax to specify additional simulated memory regions.  [...]
> 
> Er, are you sure about this?

Uh, good point, thanks for pointing that out.  Sorry - I was thinking
of another sh simulator.  There are a few stragglers in sim/*,
including the old "sh", that don't use enough common code to do this
configuration in a uniform way.  This hegemony is what the sim/common,
and the later sid frameworks have been aiming to correct, but these
old ports just won't go away by themselves. :-)

Anyway, gazing at sim/sh/interp.c, there is a possibly useful "sim
set-memory-size NUMBITS" gdb command, with a similar unadorned
"sh-*-run PROGRAM NUMBITS" command line argument.


- FChE


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-01-17 21:50 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-01-17 10:10 How to map memory for SH simulator? William A. Gatliff
2002-01-17 11:50 ` Frank Ch. Eigler
2002-01-17 12:14   ` Andrew Cagney
2002-01-17 13:50     ` Frank Ch. Eigler

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox