From: Holger Blasum <holgerlists@blasum.net>
Cc: guile-user@gnu.org
Subject: Re: stack overflow problem
Date: Mon, 13 Feb 2006 19:08:26 +0100 [thread overview]
Message-ID: <20060213180826.GA19741@tosh> (raw)
In-Reply-To: <87fymxlwzf.fsf@www.williamxu.com>
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
On 02-05, William Xu wrote:
> Yeah, i understand that. But i thought this ought to be done
> automatically in some way, not requiring user to do this manually, which
> would make codes less readable, isn't it?
(debug-set! stack 0)
would do the trick (disabling stack depth management) afaik?
--
Holger Blasum +49-174-7313590 (gsm) GnuPG 1024D/ACDFC3B769DC1ED66B47
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-02-13 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 10:54 stack overflow problem William Xu
2006-02-04 23:03 ` Chusslove Illich
2006-02-05 1:18 ` Stephen Compall
2006-02-05 14:08 ` William Xu
2006-02-13 18:08 ` Holger Blasum [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-04 17:09 William Xu
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060213180826.GA19741@tosh \
--to=holgerlists@blasum.net \
--cc=guile-user@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).