From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9507 invoked by alias); 13 Apr 2002 16:33:10 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 9499 invoked from network); 13 Apr 2002 16:33:09 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 13 Apr 2002 16:33:09 -0000 Received: from theotherone.redhat-remotie.org (remus.sfbay.redhat.com [172.16.27.252]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id JAA09666; Sat, 13 Apr 2002 09:33:07 -0700 (PDT) Received: from localhost (localhost.fidalgo.net [127.0.0.1]) by theotherone.redhat-remotie.org (Postfix) with ESMTP id 06A0BBB255; Sat, 13 Apr 2002 09:33:58 -0700 (PDT) Date: Sat, 13 Apr 2002 09:33:00 -0000 From: Don Howard X-X-Sender: To: Eli Zaretskii Cc: , , , , , Subject: Re: [RFA] Avoid recursivly defined user functions. In-Reply-To: <3277-Sat13Apr2002113850+0300-eliz@is.elta.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-04/txt/msg00490.txt.bz2 How's this? 2002-04-13 Don Howard From Eli Zaretskii * 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 > > > > +@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