Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Avoid recursivly defined user functions.
Date: Thu, 11 Apr 2002 12:08:00 -0000	[thread overview]
Message-ID: <20020411150835.A15229@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0204111053541.25679-100000@theotherone.redhat-remotie.org>

On Thu, Apr 11, 2002 at 10:55:26AM -0700, Don Howard wrote:
> On Tue, 9 Apr 2002, Don Howard wrote:
> 
> > On Tue, 9 Apr 2002, Paul Hilfinger wrote:
> > 
> > > 
> > > > How about something even simpler - track user command depth at runtime? 
> > > > Set an absurd limit, like 1024 deep, if we can handle that in a
> > > > normal-sized stack limit.  Then complain if we hit it at runtime.
> > > 
> > > I completely agree with this.  After all, if you were willing to
> > > contemplate outlawing recursion altogether, you certainly won't LOSE
> > > anything by Daniel's approach, and you gain everything you wanted in
> > > the first place---to avoid crashing GDB.  
> > > 
> > > Paul
> > > 
> > 
> > 
> > I like this approach, also.  
> > 
> 
> 
> 2002-04-11  Don Howard  <dhoward@redhat.com>
> 
> 	* cli/cli-cmds.c (init_cli_cmds): Add new user settable value:
> 	max_user_call_depth.
> 	(init_cmd_lists): Initialize the new value;
> 	* cli/cli-script.c (execute_user_command): Limit the call depth of
> 	user defined commands.  This avoids a core-dump when user commands
> 	are infinitly recursive.

Well, I like it.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-04-11 19:08 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 [this message]
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
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=20020411150835.A15229@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@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