Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: bgat@billgatliff.com
Cc: gdb@sources.redhat.com
Subject: Re: How to map memory for SH simulator?
Date: Thu, 17 Jan 2002 11:50:00 -0000	[thread overview]
Message-ID: <o5wuyglpt4.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <20020117121015.A27796@saturn.billgatliff.com>


"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


  reply	other threads:[~2002-01-17 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 10:10 William A. Gatliff
2002-01-17 11:50 ` Frank Ch. Eigler [this message]
2002-01-17 12:14   ` Andrew Cagney
2002-01-17 13:50     ` Frank Ch. Eigler

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=o5wuyglpt4.fsf@toenail.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=bgat@billgatliff.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