Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Don Howard <dhoward@redhat.com>
To: <gdb-patches@sources.redhat.com>
Subject: [RFA] Avoid recursivly defined user functions.
Date: Wed, 03 Apr 2002 14:09:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0204031358120.18114-100000@theotherone.redhat-remotie.org> (raw)



Executing a recursively defined user function results in a core-dump from 
gdb:

(gdb) define foo
Type commands for definition of "foo".
End with a line saying just "end".
>foo
>end
(gdb) foo
Segmentation fault (core dumped)


The following patch catches recursive user function definitions and 
disallowes them:



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

	* cli/cli-script.c (define_command): Avoid recursivly defined user
	commands.


Index: 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-script.c        2002/03/17 19:53:39     1.11
+++ cli-script.c        2002/04/03 22:07:36
@@ -1099,6 +1099,13 @@ define_command (char *comname, int from_
   sprintf (tmpbuf, "Type commands for definition of \"%s\".", comname);
   cmds = read_command_lines (tmpbuf, from_tty);
 
+  {
+    struct command_line *c;
+    for (c=cmds; c; c=c->next)
+      if (strcmp (c->line, comname) == 0)
+       error ("Recursive user command definitions are not supported.");
+  }
+
   if (c && c->class == class_user)
     free_command_lines (&c->user_commands);


-- 
dhoward@redhat.com
gdb engineering




             reply	other threads:[~2002-04-03 22:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 14:09 Don Howard [this message]
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
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.0204031358120.18114-100000@theotherone.redhat-remotie.org \
    --to=dhoward@redhat.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