From: "liu lijuan" <lljchina@hotmail.com>
To: ac131313@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: about gdb's compiled-in simulator
Date: Sun, 16 Mar 2003 14:29:00 -0000 [thread overview]
Message-ID: <F159MuBeZVo2d3gwhDC000005fc@hotmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 1270 bytes --]
>From: Andrew Cagney <ac131313@redhat.com>
>To: liu lijuan <lljchina@hotmail.com>
>CC: gdb@sources.redhat.com
>Subject: Re: about gdb's compiled-in simulator
>Date: Thu, 13 Mar 2003 12:08:06 -0500
>
> >
> > After gdb get the commands from keyboard,does gdb put these commands
into a cmd_buffer,and then gdb and compiled-in simulator access the
cmd_buffer together?
> > Or does gdb and compiled-in simultor have any rules about the request
and reply of commands ? Thanks for your help!
>
>GDB calls:
>
>include/gdb/remote-sim.h:sim_do_command()
>
>with the command string in a buffer. There isn't any expected return
>value (the command can't fail).
>
>Andrew
what you mean is that gdb call sim_do_command() to deal with the
commands in command line which send to simulator.But after disable this
function in all files like this //sim_do_command(),then I recompile
cross-gdb,and it can work normally
and gdb and simulator can deal with commands as usual.So I still feel
puzzled how simulator identify the commands from gdb command line.
please can you tell me why?
Thanks!
liu
_________________________________________________________________
ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com
next reply other threads:[~2003-03-16 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 14:29 liu lijuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 2:48 liu lijuan
2003-03-13 17:08 ` Andrew Cagney
2003-03-13 2:47 liu lijuan
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=F159MuBeZVo2d3gwhDC000005fc@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).