From: "Bill Schottstaedt" <bil@ccrma.Stanford.EDU>
Subject: Re: Guile 1.7.91 has been released.
Date: Tue, 14 Feb 2006 13:36:05 -0800 [thread overview]
Message-ID: <20060214213003.M64292@ccrma.Stanford.EDU> (raw)
In-Reply-To: <873bimsp8w.fsf@zip.com.au>
Andy Wingo says:
> I once did some painful CVS bisection, which for the compiler flags I was
> using brought it back to the introduction of the inline keyword in 2002
> or something.
Perhaps you're on to something -- the "inline" business reminded me of
the old pstate bug where a variable was being optimized off the stack
causing premature gc, or something like that. So, I rebuilt guile using
-g3 and not -O2, and the build ran to completion! Unfortunately, it's still
not right; guile doesn't segfault but I get:
/home/bil/test/ bin/guile
Backtrace:
In unknown file:
?: 130* [syntmp-gen-syntax-1074 #(syntax-object # #) #(syntax-object # #) ...]
?: 131 (if (syntmp-id?-115 syntmp-e-1110) (let* (#) (let* # #)) ...)
...
?: 132 [call-with-values #<procedure #f ()> #<procedure #f #>]
?: 133 (@call-with-values (producer consumer))
?: 134* [#<procedure #f ()>]
?: 135* [syntmp-gen-syntax-1074 #(syntax-object # #) #(syntax-object begin #) ...]
?: 136 (if (syntmp-id?-115 syntmp-e-1110) (let* (#) (let* # #)) ...)
...
?: 137 (if # # #)
?: 138* [syntmp-ellipsis?-160 #(syntax-object begin (# # # #))]
?: 139 (and # #)
...
?: 140 [syntmp-free-id=?-138 #(syntax-object begin #) #(syntax-object ... #)]
?: 141 (and (eq? # #) (eq? # #))
?: 142* [eq? ...
?: 143* (let* ((syntmp-x-885 syntmp-i-883)) (let* (#) (if # # syntmp-e-886)))
?: 144 (let* (#) (if # # syntmp-e-886))
?: 145* (if # # syntmp-x-885)
?: 146* [syntmp-syntax-object?-101 #(syntax-object begin (# # # #))]
?: 147 (and (vector? syntmp-x-1008) (= (vector-length syntmp-x-1008) 3) ...)
?: 148* [= ...
?: 149* (vector-length syntmp-x-1008)
<unnamed port>: In expression (vector-length syntmp-x-1008):
<unnamed port>: Stack overflow
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-14 21:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
2006-02-12 23:46 ` Michael Tuexen
2006-02-14 21:50 ` Marius Vollmer
2006-02-18 23:45 ` Han-Wen Nienhuys
2006-02-20 20:59 ` Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys
2006-02-13 9:41 ` Ludovic Courtès
2006-02-13 19:50 ` Marius Vollmer
2006-02-14 9:22 ` Ludovic Courtès
2006-02-14 19:39 ` Marius Vollmer
2006-02-13 12:49 ` Bill Schottstaedt
2006-02-13 21:35 ` Kevin Ryde
2006-02-13 22:33 ` Bill Schottstaedt
2006-02-13 22:50 ` Kevin Ryde
2006-02-13 23:35 ` Bill Schottstaedt
2006-02-14 0:58 ` Kevin Ryde
2006-02-14 1:28 ` Kevin Ryde
2006-02-14 21:36 ` Bill Schottstaedt [this message]
2006-02-15 0:03 ` Kevin Ryde
2006-02-15 7:56 ` Ludovic Courtès
2006-02-15 12:37 ` Guile 1.7.91 has been released (x86-64 segfault) Bill Schottstaedt
2006-02-14 9:27 ` Guile 1.7.91 has been released Ludovic Courtès
2006-02-13 15:31 ` Bill Schottstaedt
2006-02-14 8:50 ` Andy Wingo
2006-02-20 18:36 ` Neil Jerram
2006-02-20 20:04 ` Bill Schottstaedt
2006-02-13 18:40 ` Bill Schottstaedt
2006-02-14 11:35 ` Han-Wen Nienhuys
2006-02-14 21:32 ` Marius Vollmer
2006-02-14 13:58 ` Ludovic Courtès
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=20060214213003.M64292@ccrma.Stanford.EDU \
--to=bil@ccrma.stanford.edu \
/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).