unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Updating NEWS for 1.6.8 release.
Date: Mon, 17 Oct 2005 18:40:37 +0100	[thread overview]
Message-ID: <87y84s82ju.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87psq5awmb.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 17 Oct 2005 09:08:12 +1000")

Kevin Ryde <user42@zip.com.au> writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> Thanks.  In this case, I'm pretty sure my bug fixes don't qualify as
>> NEWS.
>
> What is the continuations versus stack bit you added some tests for?
> Is it a fix for something?

Yes, for `(call/cc make-stack)'.  make-stack is supposed to be able to
construct a stack from a continuation, a debug object, or from `#t',
which means the current evaluation stack.  But the make-stack code was
missing a lot of the relocations that are needed in the
continuation case.  The symptom was a segmentation fault.

I forget now exactly how I discovered this, though.  Is it worth me
trying to dig that up?

       Neil



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


  reply	other threads:[~2005-10-17 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 18:46 Updating NEWS for 1.6.8 release Rob Browning
2005-10-15 21:40 ` Neil Jerram
2005-10-16  3:10   ` Rob Browning
2005-10-16 20:38     ` Neil Jerram
2005-10-16 23:08       ` Kevin Ryde
2005-10-17 17:40         ` Neil Jerram [this message]
2005-10-17 18:29           ` Rob Browning
2005-10-17 18:51             ` Neil Jerram
2005-10-16 18:43 ` Rob Browning
2005-10-16 23:16   ` Kevin Ryde
2005-10-16 23:43     ` Rob Browning
2005-10-16 23:12 ` Kevin Ryde
2005-10-16 23:17   ` Rob Browning

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=87y84s82ju.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).