unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: Rainer Tammer <tammer@tammer.net>, guile-devel@gnu.org
Subject: Re: stack overflow
Date: Wed, 13 Feb 2008 20:40:24 +0000	[thread overview]
Message-ID: <87wsp83807.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87ir0tvx6e.fsf@inria.fr> (Ludovic Courtès's message of "Wed, 13 Feb 2008 13:49:13 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Hi,
>
> Rainer Tammer <tammer@tammer.net> writes:
>
>> I added -qtune=auto but this did not solve the problem...
>> I will try other optimization settings...
>
> You did "make clean all" after reconfiguring with your `CFLAGS', right?
> Also, do the actual compilation command lines show that your `CFLAGS'
> settings were taken into account?
>
> Besides, you can try adding "(debug-set! stack 40000)" to your
> `~/.guile' and see if that makes a difference, and increase it until it
> works, just to get an idea.

[moving over to guile-devel...]

Not to disagree with anything that's already been said in this
thread...  But I wonder if there is a way to make Guile's stack
overflow checking a bit less fragile - i.e. less subject to the
behaviour of particular compilers / OSs / optimization options?

I think all we're really trying to do, with the stack overflow
feature, is guard against a suspected infinite recursion, without
resorting to crashing the whole program.  Perhaps there is a cunning
way to do that without having to set an arbitrary stack depth limit?
Any ideas would be most welcome.

Regards,
        Neil





       reply	other threads:[~2008-02-13 20:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <47B2A8DF.9070004@tammer.net>
     [not found] ` <87tzkd8bvz.fsf@gnu.org>
     [not found]   ` <87ejbh8ben.fsf@gnu.org>
     [not found]     ` <47B2D88F.1040505@tammer.net>
     [not found]       ` <87ir0tvx6e.fsf@inria.fr>
2008-02-13 20:40         ` Neil Jerram [this message]
2008-02-14  8:48           ` stack overflow Ludovic Courtès
2008-02-14 10:26             ` Mikael Djurfeldt
2008-02-14 11:25               ` Ludovic Courtès
2008-02-14 11:39                 ` Mikael Djurfeldt
2008-02-25 21:52                   ` Neil Jerram
2008-07-16 12:34                     ` Ludovic Courtès
2008-09-12 20:47                     ` Stack calibration Ludovic Courtès
2008-09-27 18:20                       ` Neil Jerram
2008-09-28 20:05                         ` Ludovic Courtès
2008-09-30 22:10                           ` Neil Jerram
2008-10-02  8:25                             ` Andy Wingo
2008-10-02  8:38                               ` Neil Jerram
2008-10-02 22:30                             ` Neil Jerram
2008-10-06 22:32                               ` Ludovic Courtès
2008-10-06 23:11                                 ` Neil Jerram
2008-10-09 22:53                                   ` Neil Jerram
2008-10-10 13:22                                     ` Greg Troxel
2008-10-10 18:04                                       ` Neil Jerram
2008-10-10 18:28                                         ` Greg Troxel
2008-10-10 18:41                                           ` Neil Jerram
2008-10-11 17:22                                     ` Ludovic Courtès
2008-10-12 15:59                                       ` Neil Jerram
2008-10-12 21:16                                         ` Neil Jerram
2008-10-13 21:37                                           ` Neil Jerram
2008-10-14  7:25                                           ` Ludovic Courtès
2008-10-17 20:49                                             ` Neil Jerram
2008-10-14  7:19                                         ` Ludovic Courtès
2008-09-28 20:07                         ` Ludovic Courtès
2008-09-30 22:11                           ` Neil Jerram
2008-02-17  1:38           ` stack overflow Han-Wen Nienhuys
2008-02-17  9:20             ` Mikael Djurfeldt

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=87wsp83807.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=tammer@tammer.net \
    /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).