Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: liu lijuan <lljchina@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: a question about gdb and simulator
Date: Wed, 26 Feb 2003 14:51:00 -0000	[thread overview]
Message-ID: <3E5CD4E1.8010809@redhat.com> (raw)
In-Reply-To: <F1412cFXvmBUCsQrU6W00003563@hotmail.com>

> 
>    We are doing graduate design about SOC design tool, and we want to extend GNU debugger隆炉s some functions, and do a simulator and debugger environment. We use SystemC to simulate the procedure of CPU simulator, and this simulator is a part of hardware system.  During the simulation, CPU simulator needs a soft debugger. We want to use gdb as its debugger. We know that gdb supports built-in CPU simulator, but our simulator isn隆炉t built-in. But we don隆炉t know how gdb exchange information with built-in simulator and control the run of built-in CPU simulator. On this condition, we intend to apply the communication method between gdb and built-in CPU simulator to our design. Our simulator doesn隆炉t work as gdb隆炉s ISS , and also doesn隆炉t run in remote manner, therefore we think 隆掳gdb remote serial protocol隆卤 can not be used in our design. Because our CPU simulator run in local manner (simulator and gdb run in the same machine), we think the same mechanism may be used in our desig
n.
>    If you have time, can you help us and provide us some reference about our work?
>    Thanks a lot!

Assuming you have the GDB sources in front of you, look at the file
"src/include/gdb/remote-sim.h".  It defines the GDB-SIM interfaces that
GDB currently uses.

Also, I'd not dismiss the "remote" method.  Some simulators use that
interface as well.

Andrew



  reply	other threads:[~2003-02-26 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 13:06 liu lijuan
2003-02-26 14:51 ` Andrew Cagney [this message]
2003-02-26 18:04 Fyles, Matthew
     [not found] <F84byfA34cnFqUob5MF00027426@hotmail.com>
2003-02-27 16:36 ` Andrew Cagney

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=3E5CD4E1.8010809@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=lljchina@hotmail.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