unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Alexandre Duret-Lutz <Alexandre.Duret-Lutz@lip6.fr>
Subject: segfault on incorrect code
Date: 22 Jan 2004 17:49:51 +0100	[thread overview]
Message-ID: <2004-01-22-17-49-52+19695+adl@gnu.org> (raw)

Seeing a thread named "core dump" remembered me an old bug I
stumbled upon years ago (in guile 1.3), but never reported. 
It seems to be still present in recent versions.

% guile
guile> (version)
"1.6.4"
guile> (define (foo a b c) (< b c))
guile> (sort '(3 2 1) foo)
zsh: segmentation fault  guile

The code is obviously wrong, but maybe sort could check the
arity of its last argument.
-- 
Alexandre Duret-Lutz



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


             reply	other threads:[~2004-01-22 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 16:49 Alexandre Duret-Lutz [this message]
2004-02-13  0:11 ` segfault on incorrect code Marius Vollmer
2004-02-14  0:07 ` Kevin Ryde
2004-02-14  0:33   ` Kevin Ryde

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=2004-01-22-17-49-52+19695+adl@gnu.org \
    --to=alexandre.duret-lutz@lip6.fr \
    /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).