From: "liu lijuan" <lljchina@hotmail.com>
To: ac131313@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: command line interface
Date: Fri, 07 Mar 2003 05:40:00 -0000 [thread overview]
Message-ID: <F37Nh8b1SWpnrScDBm0000120ca@hotmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 1419 bytes --]
>From: Andrew Cagney <ac131313@redhat.com>
>To: liu lijuan <lljchina@hotmail.com>
>CC: gdb@sources.redhat.com
>Subject: Re: command line interface
>Date: Thu, 06 Mar 2003 15:20:39 -0500
>
> >
> > Does the communication between gdb and compiled-in target simulator
follow any rules? for example,there is "remote debug interface " between
gdb and ARMulator,and "remote serial protocol"between gdb and remote
target.
> > the compiled-in simulator receive the command from gdb command line
interface and return the info to gdb.how to deal with the procedure?Is
there any protocol?
>
>`it depends'
>
>A few, but not many, simulators allow sim specific commands via the
>`sim' command prefix. The MIPS is one, I don't think the arm is one
though.
>
>Andrew
I don't understand your answer very clearly.Do you mean that gdb transfer
command to simulator via "sim <command>"? What I want to say is how gdb and
simulator deal with their commands .for example, when you open a exec file
to debug,then connect this to simulator via "target sim",then load this
file to simulator,at last you can debug it with all kinds of commands.I
just want to make this procedure clearly.How can gdb and simulator identify
the commands from one to another?
_________________________________________________________________
ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn
next reply other threads:[~2003-03-07 5:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 5:40 liu lijuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 6:34 liu lijuan
2003-03-06 10:36 ` Richard Earnshaw
2003-03-06 20:20 ` 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=F37Nh8b1SWpnrScDBm0000120ca@hotmail.com \
--to=lljchina@hotmail.com \
--cc=ac131313@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).