unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: 1.8 make check failing in popen.test
Date: Thu, 31 Aug 2006 10:24:25 +1000	[thread overview]
Message-ID: <878xl5ah1i.fsf@zip.com.au> (raw)
In-Reply-To: <87irka4q8f.fsf@raven.defaultvalue.org> (Rob Browning's message of "Wed, 30 Aug 2006 00:50:08 -0700")

Rob Browning <rlb@defaultvalue.org> writes:
>
>                                 ;;(dbg-out (list 'pt-entry pt-entry))
>                                 ...
>
>   ERROR: popen.test: open-output-pipe: no duplicate - arguments:
>   ((wrong-type-arg "list-copy" "Wrong type argument in position ~A: ~S"
>   (1 (pt-entry . #<freed cell 0x40305830; GC missed a reference>))
>   ((pt-entry . #<freed cell 0x40305830; GC missed a reference>))))

It's possible the complaint is about the `list' call.  I changed
`list' to be implemented using scm_list_copy, which of course reports
itself as `list-copy' if the list is improper.  But I can't think how
an improper list could arrive there from a "(list x y)" call.

>   (pt-entry #<freed cell 0x40643c18; GC missed a reference>)

I suppose that's the killer, a port gc-ed prematurely.  Perhaps
there'd be some significance in which one it was.  port-for-each looks
pretty safe, maybe the port table has gone bad earlier.



Not sure how this would relate to the following bit you posted
before.  If this bit was taken literally it'd sound like something
evil in scm_call_1 I suppose.

>   ERROR: popen.test: close-pipe: exit 0 - arguments: ((wrong-number-of-args #f "Wrong number of arguments to ~A" (#<procedure #f (pt-entry)>) #f))


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


  reply	other threads:[~2006-08-31  0:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-23  8:37 1.8 make check failing in popen.test Rob Browning
2006-07-23 22:36 ` Kevin Ryde
2006-07-23 23:12   ` Rob Browning
2006-07-24  7:25     ` Ludovic Courtès
2006-07-30  1:59       ` Rob Browning
2006-08-15  8:35 ` Rob Browning
2006-08-15 23:13   ` Kevin Ryde
2006-08-16  1:18     ` Rob Browning
2006-08-16 23:26       ` Kevin Ryde
2006-08-18  3:01         ` Rob Browning
2006-08-21 23:38           ` Kevin Ryde
2006-08-22  2:03             ` Rob Browning
2006-08-25  1:16               ` Kevin Ryde
2006-08-25  2:39                 ` Rob Browning
2006-08-27 20:06                   ` Rob Browning
2006-08-27 20:22                     ` Rob Browning
2006-08-30  7:50             ` Rob Browning
2006-08-31  0:24               ` Kevin Ryde [this message]
2006-08-31  6:28                 ` Rob Browning
2006-09-04  2:45                   ` Rob Browning
2006-09-07 20:46                     ` Kevin Ryde
2006-09-08  2:45                       ` Rob Browning
2006-09-08 23:05                         ` Kevin Ryde
2006-09-09 12:52                           ` Marius Vollmer
2006-09-09 16:39                             ` Rob Browning
2006-09-10 16:24                               ` Rob Browning
2006-09-11  1:16                                 ` Rob Browning
2006-09-11  6:40                                   ` Neil Jerram
2006-09-11 15:57                                     ` Rob Browning
2006-09-11 17:40                                       ` Neil Jerram

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=878xl5ah1i.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --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).