From: Michael Snyder <msnyder@redhat.com>
To: Don Howard <dhoward@redhat.com>
Cc: Hilfinger@cs.berkeley.edu, Daniel Jacobowitz <drow@mvista.com>,
Andreas Schwab <schwab@suse.de>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA] Avoid recursivly defined user functions.
Date: Thu, 11 Apr 2002 13:55:00 -0000 [thread overview]
Message-ID: <3CB5F583.8B2E6707@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204111053541.25679-100000@theotherone.redhat-remotie.org>
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.
So do I. ;-)
> >
>
> 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.
>
> Index: cli/cli-cmds.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/cli/cli-cmds.c,v
> retrieving revision 1.18
> diff -p -u -w -r1.18 cli-cmds.c
> --- cli/cli-cmds.c 28 Mar 2002 01:35:56 -0000 1.18
> +++ cli/cli-cmds.c 11 Apr 2002 17:30:58 -0000
> @@ -80,6 +80,9 @@ static void shell_escape (char *, int);
>
> void apropos_command (char *, int);
>
> +/* Limit the call depth of user-defined commands */
> +int max_user_call_depth;
> +
> /* Define all cmd_list_elements. */
>
> /* Chain containing all defined commands. */
> @@ -606,6 +609,8 @@ show_debug (char *args, int from_tty)
> void
> init_cmd_lists (void)
> {
> + max_user_call_depth = 1024;
> +
> cmdlist = NULL;
> infolist = NULL;
> enablelist = NULL;
> @@ -823,4 +828,11 @@ With no arguments, run an inferior shell
> Argument is the name of the user defined command.\n\
> With no argument, show definitions of all user defined commands.", &showlist);
> add_com ("apropos", class_support, apropos_command, "Search for commands matching a REGEXP");
> +
> + add_show_from_set (
> + add_set_cmd ("max_user_call_depth", no_class, var_integer,
> + (char *) &max_user_call_depth,
> + "Set the max call depth for user-defined commands.\n",
> + &setlist),
> + &showlist);
> }
> Index: cli/cli-script.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/cli/cli-script.c,v
> retrieving revision 1.11
> diff -p -u -w -r1.11 cli-script.c
> --- cli/cli-script.c 17 Mar 2002 19:53:39 -0000 1.11
> +++ cli/cli-script.c 11 Apr 2002 17:30:59 -0000
> @@ -247,6 +247,15 @@ execute_cmd_post_hook (struct cmd_list_e
> }
>
> /* Execute the command in CMD. */
> +void
> +do_restore_user_call_depth (void * call_depth)
> +{
> + int * depth = call_depth;
> + /* We will be returning_to_top_level() at this point, so we want to
> + reset our depth. */
> + (*depth) = 0;
> +}
> +
>
> void
> execute_user_command (struct cmd_list_element *c, char *args)
> @@ -254,6 +263,8 @@ execute_user_command (struct cmd_list_el
> register struct command_line *cmdlines;
> struct cleanup *old_chain;
> enum command_control_type ret;
> + static int user_call_depth = 0;
> + extern int max_user_call_depth;
>
> old_chain = setup_user_args (args);
>
> @@ -262,6 +273,11 @@ execute_user_command (struct cmd_list_el
> /* Null command */
> return;
>
> + if (user_call_depth++ > max_user_call_depth)
> + error ("Max user call depth exceeded -- command aborted\n");
> +
> + old_chain = make_cleanup (do_restore_user_call_depth, &user_call_depth);
> +
> /* Set the instream to 0, indicating execution of a
> user-defined function. */
> old_chain = make_cleanup (do_restore_instream_cleanup, instream);
> @@ -277,6 +293,8 @@ execute_user_command (struct cmd_list_el
> cmdlines = cmdlines->next;
> }
> do_cleanups (old_chain);
> +
> + user_call_depth--;
> }
>
> enum command_control_type
>
> --
> dhoward@redhat.com
> gdb engineering
next prev parent reply other threads:[~2002-04-11 20:55 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 [this message]
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=3CB5F583.8B2E6707@redhat.com \
--to=msnyder@redhat.com \
--cc=Hilfinger@cs.berkeley.edu \
--cc=dhoward@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.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