From: Daniel Jacobowitz <drow@mvista.com>
To: Don Howard <dhoward@redhat.com>
Cc: Andreas Schwab <schwab@suse.de>,
Michael Snyder <msnyder@redhat.com>,
Hilfinger@cs.berkeley.edu, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Avoid recursivly defined user functions.
Date: Tue, 09 Apr 2002 14:05:00 -0000 [thread overview]
Message-ID: <20020409170456.A14389@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0204091325540.25679-100000@theotherone.redhat-remotie.org>
On Tue, Apr 09, 2002 at 02:01:13PM -0700, Don Howard wrote:
> I think I can detect mutual recursion by walking through the body of each
> user-defined command (recursivly). This amounts to static recursion
> detection.
>
> I think I could track simple recursion depth at runtime.
>
> I don't see how to track mutual recursion depth at runtime. Maybe do the
> static recursion detection and recursivly flag user-defined commands in
> the body?
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.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-09 21:05 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 [this message]
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=20020409170456.A14389@nevyn.them.org \
--to=drow@mvista.com \
--cc=Hilfinger@cs.berkeley.edu \
--cc=dhoward@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