From: Matt Rice <ratmice@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] document target sim args & arm options
Date: Fri, 26 Mar 2010 15:17:00 -0000 [thread overview]
Message-ID: <8ba6bed41003260817wf3494c9l7371622965ce7558@mail.gmail.com> (raw)
In-Reply-To: <837hozgmzm.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 483 bytes --]
On Fri, Mar 26, 2010 at 7:45 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Fri, 26 Mar 2010 07:10:07 -0700
>> From: Matt Rice <ratmice@gmail.com>
>>
>> +@item target sim @r{[}@var{simargs}@r{]} @r{...}
>
> This will look better if you use @dots{} instead of @r{...}.
>
> Okay with this change.
Thanks,
attached is an updated patch, also changing another occurance of @r{...}
forgot to mention i don't have commit access, there is a request in the queue,
so whatever is easiest.
[-- Attachment #2: simargs.diff --]
[-- Type: application/octet-stream, Size: 2105 bytes --]
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 4bef3f0..56dbe5d 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -3872,7 +3872,7 @@ A call to @code{exec}. This is currently only available for HP-UX
and @sc{gnu}/Linux.
@item syscall
-@itemx syscall @r{[}@var{name} @r{|} @var{number}@r{]} @r{...}
+@itemx syscall @r{[}@var{name} @r{|} @var{number}@r{]} @dots{}
@cindex break on a system call.
A call to or return from a system call, a.k.a.@: @dfn{syscall}. A
syscall is a mechanism for application programs to request a service
@@ -14899,7 +14899,7 @@ useful if you have some other way of getting the stub to the target
system, and you can put it somewhere in memory where it won't get
clobbered by the download.
-@item target sim
+@item target sim @r{[}@var{simargs}@r{]} @dots{}
@cindex built-in simulator target
Builtin CPU simulator. @value{GDBN} includes simulators for most architectures.
In general,
@@ -17295,6 +17295,25 @@ well as the Angel monitor.
Show the setting of RDI heartbeat packets.
@end table
+@table @code
+@item target sim @r{[}@var{simargs}@r{]} @dots{}
+The @value{GDBN} ARM simulator accepts the following optional arguments.
+
+@table @code
+@item --swi-support=@var{type}
+Tell the simulator which SWI interfaces to support.
+@var{type} may be a comma separated list of the following values.
+The default value is @code{all}.
+
+@table @code
+@item none
+@item demon
+@item angel
+@item redboot
+@item all
+@end table
+@end table
+@end table
@node M32R/D
@subsection Renesas M32R/D and M32R/SDI
diff --git a/gdb/remote-sim.c b/gdb/remote-sim.c
index 9f1adc7..96b45de 100644
--- a/gdb/remote-sim.c
+++ b/gdb/remote-sim.c
@@ -889,7 +889,7 @@ init_gdbsim_ops (void)
{
gdbsim_ops.to_shortname = "sim";
gdbsim_ops.to_longname = "simulator";
- gdbsim_ops.to_doc = "Use the compiled-in simulator.";
+ gdbsim_ops.to_doc = "Use the compiled-in simulator. Any arguments will be passed on to the simulator.";
gdbsim_ops.to_open = gdbsim_open;
gdbsim_ops.to_close = gdbsim_close;
gdbsim_ops.to_detach = gdbsim_detach;
next prev parent reply other threads:[~2010-03-26 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 14:10 Matt Rice
2010-03-26 14:46 ` Eli Zaretskii
2010-03-26 15:17 ` Matt Rice [this message]
2010-03-26 15:25 ` Eli Zaretskii
2010-03-26 15:33 ` Matt Rice
2010-03-27 9:02 ` Eli Zaretskii
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=8ba6bed41003260817wf3494c9l7371622965ce7558@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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