unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys  <hanwen@xs4all.nl>
Cc: jantien@xs4all.nl
Subject: segfault in CVS HEAD
Date: Sat, 12 Jun 2004 23:12:34 +0200	[thread overview]
Message-ID: <16587.29122.106192.358092@localhost.localdomain> (raw)


(I think I've  already sent this, but I couldn't fidn a copy in my
outbox.)

this is with current CVS  head

	byrd:~/usr/src/guile/libguile$ guile --debug t.scm
	Backtrace:
	In unknown file:
	   ?: 0* [primitive-load "t.scm"]
	In t.scm:
	   1: 1* Segmentatie fout
	byrd:~/usr/src/guile/libguile$ cat t.scm
	(defiaine  blub  (cons (quote (1 . 2)) 2))


for some reason, GUILE unmemoizes the procedure during print; of
course, the expression is not memoized, since evaluation stops after
"defiaine". I've seen similar problems with invocations of
procedure-source on valid code.

Please fix - this is a serious error.


-- 

 Han-Wen Nienhuys   |   hanwen@xs4all.nl   |   http://www.xs4all.nl/~hanwen 



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2004-06-12 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12 21:12 Han-Wen Nienhuys [this message]
2004-06-12 21:14 ` segfault in CVS HEAD Han-Wen Nienhuys
2004-06-12 22:26   ` Han-Wen Nienhuys
2004-06-20  7:15     ` Dirk Herrmann
2004-06-20 20:43       ` Han-Wen Nienhuys
2004-06-21 21:08         ` Dirk Herrmann
2004-06-22 10:12           ` Jan Nieuwenhuizen
2004-06-22 20:31         ` Han-Wen Nienhuys
2004-06-26  6:02           ` Dirk Herrmann
2004-06-26  8:26             ` Han-Wen Nienhuys
     [not found] <40DD5A64.60300@ccrma>
     [not found] ` <40DEC836.3010806@dirk-herrmanns-seiten.de>
     [not found]   ` <40E2917A.7010106@ccrma>
2004-07-14  7:22     ` Dirk Herrmann
2004-07-14 12:36       ` Dale P. Smith
2004-08-21  8:00     ` Dirk Herrmann
2004-08-23 10:43       ` Bill Schottstaedt

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=16587.29122.106192.358092@localhost.localdomain \
    --to=hanwen@xs4all.nl \
    --cc=jantien@xs4all.nl \
    /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).