unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: linasvepstas@gmail.com, "Ludovic Courtès" <ludo@gnu.org>,
	guile-devel@gnu.org
Subject: Re: GNU Guile 1.9.0 released (alpha)
Date: Sun, 21 Jun 2009 13:36:03 +0100	[thread overview]
Message-ID: <871vpdbw7g.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m363eprhox.fsf@pobox.com> (Andy Wingo's message of "Sun\, 21 Jun 2009 12\:42\:54 +0200")

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

Andy Wingo <wingo@pobox.com> writes:

> Hi Mike,
>
> On Sun 21 Jun 2009 08:31, Mike Gran <spk121@yahoo.com> writes:
>
>> Not really in a position to help, since I'm still AFK, but, 
>> somewhere along the line I pushed this patch to r6rs vectors
>> in the String_abstraction2 tree.
>
> Took me a little while to understand it, but it seems the patch is
> right. I committed and pushed it to master. Linas, can you try again?
>
> Thanks much!

I've pushed a deterministic test for this (also below).  (In general,
when fixing something that isn't already reliably reproduced by the
build, please write a regression test if feasible.)

      Neil


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Deterministic-test-for-the-r6rs-ports.test-segmentat.patch --]
[-- Type: text/x-diff, Size: 845 bytes --]

From 4574ec212aad4df9571463ee4d45beb2607e51ad Mon Sep 17 00:00:00 2001
From: Neil Jerram <neil@ossau.uklinux.net>
Date: Sun, 21 Jun 2009 13:31:20 +0100
Subject: [PATCH] Deterministic test for the r6rs-ports.test segmentation fault

* test-suite/tests/r6rs-ports.test ("7.2.7 Input Ports"): Add (gc), to
  test the (ex-)bug in cbp_mark () when marking a closed port.
---
 test-suite/tests/r6rs-ports.test |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/test-suite/tests/r6rs-ports.test b/test-suite/tests/r6rs-ports.test
index 829258f..df12e5c 100644
--- a/test-suite/tests/r6rs-ports.test
+++ b/test-suite/tests/r6rs-ports.test
@@ -342,6 +342,7 @@
                                                     close!)))
 
       (close-port port)
+      (gc) ; Test for marking a closed port.
       closed?)))
 
 \f
-- 
1.5.6.5


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19 22:05 GNU Guile 1.9.0 released (alpha) Ludovic Courtès
2009-06-19 23:55 ` Linas Vepstas
2009-06-20  3:00 ` Linas Vepstas
2009-06-20  9:14   ` Neil Jerram
2009-06-20  9:48   ` Ludovic Courtès
2009-06-20 12:31   ` Andy Wingo
2009-06-20 18:17     ` Linas Vepstas
2009-06-21  6:31       ` Mike Gran
2009-06-21 10:42         ` Andy Wingo
2009-06-21 12:36           ` Neil Jerram [this message]
2009-06-21 18:00           ` Linas Vepstas
2009-06-21 13:58         ` Ludovic Courtès
2009-06-21 14:00           ` Ludovic Courtès
2009-06-21 15:11             ` Neil Jerram
2009-06-20 12:29 ` Andy Wingo
2009-06-20 13:35   ` Ludovic Courtès
2009-06-23 16:10 ` Changying Li
2009-06-23 20:36   ` Mike Gran

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=871vpdbw7g.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=linasvepstas@gmail.com \
    --cc=ludo@gnu.org \
    --cc=wingo@pobox.com \
    /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).