Hi, I just discovered a really subtele bug: Normaly the test are not run with --destroy-at-end. This has not many consequences yet because the only PMCs with active destruction are IOs, in fact only one test is really sensitive to t/pmc/io_4.pasm, it won't flush its buffers without --destroy-at-end. The print op also did not use this buffer so this bug didn't even show up.
There are several ways to solve this: - run the test always with --destroy-at-end - make --destroy-at-end the default and have an option --no-destroy-at-end - add a explicit flush to the test just before the end. I think we should take the second route: destroy-function should be run by default at the end of program. bye boe -- Juergen Boemmels [EMAIL PROTECTED] Fachbereich Physik Tel: ++49-(0)631-205-2817 Universitaet Kaiserslautern Fax: ++49-(0)631-205-3906 PGP Key fingerprint = 9F 56 54 3D 45 C1 32 6F 23 F6 C7 2F 85 93 DD 47
