Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Don Howard <dhoward@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: <fnasser@redhat.com>, <msnyder@redhat.com>, <schwab@suse.de>,
	<Hilfinger@cs.berkeley.edu>, <drow@mvista.com>,
	<gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Avoid recursivly defined user functions.
Date: Sat, 13 Apr 2002 09:33:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0204130931200.25679-100000@theotherone.redhat-remotie.org> (raw)
In-Reply-To: <3277-Sat13Apr2002113850+0300-eliz@is.elta.co.il>




How's this?


2002-04-13  Don Howard  <dhoward@redhat.com>

	From Eli Zaretskii <eliz@is.elta.co.il>
	* gdb.texinfo (show max-user-call-depth): Correct formatting.
	Provide a better explaination of this feature. 



Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.96
diff -p -u -w -r1.96 gdb.texinfo
--- gdb.texinfo	12 Apr 2002 22:31:23 -0000	1.96
+++ gdb.texinfo	13 Apr 2002 16:30:18 -0000
@@ -12784,9 +12784,10 @@ definitions for all user-defined command
 @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 value of @code{max-user-call-depth} controls how many levels deep a
-user-defined call chain can go.  Default is 1024.
+@itemx set max-user-call-depth
+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.
 
 @end table
 




On Sat, 13 Apr 2002, Eli Zaretskii wrote:

> > 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.
> 

-- 
dhoward@redhat.com
gdb engineering



  reply	other threads:[~2002-04-13 16:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 14:09 Don Howard
2002-04-03 14:36 ` Paul Hilfinger
2002-04-03 15:53   ` Michael Snyder
2002-04-04  3:17     ` Andreas Schwab
2002-04-09 14:01       ` Don Howard
2002-04-09 14:05         ` Daniel Jacobowitz
2002-04-09 14:09           ` Paul Hilfinger
2002-04-09 14:18             ` Don Howard
2002-04-11 10:56               ` Don Howard
2002-04-11 12:08                 ` Daniel Jacobowitz
2002-04-11 12:41                 ` Eli Zaretskii
2002-04-11 13:55                 ` Michael Snyder
2002-04-12  4:08                 ` Andreas Schwab
2002-04-12 11:28                   ` Michael Snyder
2002-04-12 12:07                     ` Fernando Nasser
2002-04-12 15:32                       ` Don Howard
2002-04-13  1:44                         ` Eli Zaretskii
2002-04-13  9:33                           ` Don Howard [this message]
2002-04-09 14:20         ` Andreas Schwab
2002-04-11 19:23 Eli Zaretskii
2002-04-13 10:04 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=Pine.LNX.4.33.0204130931200.25679-100000@theotherone.redhat-remotie.org \
    --to=dhoward@redhat.com \
    --cc=Hilfinger@cs.berkeley.edu \
    --cc=drow@mvista.com \
    --cc=eliz@is.elta.co.il \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.com \
    --cc=schwab@suse.de \
    /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