This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] Avoid recursivly defined user functions.
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- To: dhoward at redhat dot com
- Cc: fnasser at redhat dot com, msnyder at redhat dot com, schwab at suse dot de, Hilfinger at cs dot berkeley dot edu, drow at mvista dot com, gdb-patches at sources dot redhat dot com
- Date: Sat, 13 Apr 2002 11:38:51 +0300
- Subject: Re: [RFA] Avoid recursivly defined user functions.
- References: <Pine.LNX.4.33.0204121247570.25679-100000@theotherone.redhat-remotie.org>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Fri, 12 Apr 2002 15:31:30 -0700 (PDT)
> From: Don Howard <dhoward@redhat.com>
>
> +@kindex show max-user-call-depth
> +@kindex set max-user-call-depth
> +@item show max-user-call-depth
> +@item set max-user-call-depth
The second @item should be @itemx. In general, all the @item's but
the first one should be @itemx when they all pertain to the same entry
in the @table (or in @itemize list). This is so the produced text
looks like this:
[previous text]
show max-user-call-depth
set max-user-call-depth
The value of `max-user-call-depth' controls how many...
instead of this:
[previous text]
show max-user-call-depth
set max-user-call-depth
The value of `max-user-call-depth' controls how many...
where the extra line between the two @item's makes the first one look
as if the following text doesn't apply to it.
> +The value of @code{max-user-call-depth} controls how many levels deep a
> +user-defined call chain can go.
Perhaps this text is a bit more clear:
The value of @code{max-user-call-depth} controls how many recursion
levels are allowed in user-defined commands before GDB suspects an
infinite recursion and aborts the command.