[perl #22857] Parrot IO test failures
[EMAIL PROTECTED] - Mon Jun 30 07:15:44 2003]: A further data point: the tests pass if I use IMCC to assemble them, rather than assemble.pl Simon Since assemble.pl is no more, closing this ticket.
Re: [perl #22857] Parrot IO test failures
Leopold Toetsch [EMAIL PROTECTED] writes: Simon Glover [EMAIL PROTECTED] wrote: I'm getting failures in tests 1 2 in t/pmc/io.t; however, both tests seem to run fine if I run them in the debugger. valgrind does indicate, that there are unitialized items in many parts of io_buf.c. Can you tell me more about this. I know some parts code, but I still did not manage to get valgrind running on my mashine. (I don't know, if these tests even should use the bufferd IO layer, but there is for sure something wrong there) At the moment the default is to use the buffered IO. The pushing and popping of IO-Layers did not already made it to io.ops. The arbitrary failures come from uninitialized memory. I try to look into this. 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
[perl #22857] Parrot IO test failures
# New Ticket Created by Simon Glover # Please include the string: [perl #22857] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22857 Hi, I'm getting failures in tests 1 2 in t/pmc/io.t; however, both tests seem to run fine if I run them in the debugger. Furthermore, running test 1 on the command line, I find that for plain ./parrot and for ./parrot -g the test fails; for ./parrot -P and ./parrot -S, it succeeds; and for ./parrot -j, it succeeds and then segfaults. I have no idea what's going on here. Simon
Re: [perl #22857] Parrot IO test failures
A further data point: the tests pass if I use IMCC to assemble them, rather than assemble.pl Simon
Re: [perl #22857] Parrot IO test failures
Simon Glover [EMAIL PROTECTED] wrote: I'm getting failures in tests 1 2 in t/pmc/io.t; however, both tests seem to run fine if I run them in the debugger. valgrind does indicate, that there are unitialized items in many parts of io_buf.c. (I don't know, if these tests even should use the bufferd IO layer, but there is for sure something wrong there) The arbitrary failures come from uninitialized memory. Simon leo