Rob Browning <[EMAIL PROTECTED]> 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
