From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: bug in current CVS.
Date: Sun, 13 Jun 2004 11:55:54 +0200 [thread overview]
Message-ID: <87isdvpys5.fsf@zagadka.ping.de> (raw)
In-Reply-To: <16587.26076.551115.101857@localhost.localdomain> (Han-Wen Nienhuys's message of "Sat, 12 Jun 2004 22:21:48 +0200")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> byrd:~/usr/src/lilypond$ guile
> guile> (defiaine blub (cons '(1 . 2) 2))
>
> Backtrace:
> In standard input:
> 1: 0* Segmentatie fout
I can't reproduce this, unfortunately. What happens when you run
"guile -q"?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-06-13 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 20:21 bug in current CVS Han-Wen Nienhuys
2004-06-13 9:55 ` Marius Vollmer [this message]
2004-06-13 9:59 ` Han-Wen Nienhuys
2004-06-13 10:05 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2005-06-09 19:00 Han-Wen Nienhuys
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=87isdvpys5.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@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).