RE: [perl #25129] IO Buffer Test

2004-01-22 Thread Tamilmani, Arvindh Rajesh (Cognizant)
>Even if that works, PASM tests shouldn't be in t/src but in t/pmc/io.t. Sorry, I didn't know that. The attached patch is for t/pmc/io.t >leo Thanks, Arvindh biotests2.patch Description: biotests2.patch This e-mail and any files transmitted with it are for the sole use of the intended recipie

Re: [perl #25129] IO Buffer Test

2004-01-22 Thread Leopold Toetsch
Arvindh Rajesh Tamilmani <[EMAIL PROTECTED]> wrote: > name="biotests.patch" Something is wrong with these tests: patching t/src/io.t and PASM code. Even if that works, PASM tests shouldn't be in t/src but in t/pmc/io.t. leo

RE: [perl #25129] IO Buffer Test

2004-01-21 Thread Tamilmani, Arvindh Rajesh (Cognizant)
>This is a test for the buffer bug that >was discussed on p6i a few days ago. > >It does not remove the test file it makes >because I do not know a good way to do this. You may use teardown() defined in t/src/io.t The attached patch contains stripped down versions of your program that I used to s

Re: [perl #25129] IO Buffer Test

2004-01-19 Thread Leopold Toetsch
Stefan Lidman <[EMAIL PROTECTED]> wrote: [ and yet another f'up ] I've now comitted a fix for unmakeCOW not to turn off GC. So the test runs fine now with limited memory. *But*: Total memory allocated = 532480 DOD runs = 9680 Collect runs = 9660 Collect memory = 1388032592 ^

Re: [perl #25129] IO Buffer Test

2004-01-19 Thread Leopold Toetsch
Stefan Lidman <[EMAIL PROTECTED]> wrote: [ VM Panic ] > SPLIT: > substr S3, S1, 0, 1 > substr S1, 0, 1, "" The mem_allocate happens to be triggered by above string_replace, which does unmake_COW. During that GC is blocked, so we are allocating increasing blocks of memory until the

Re: [perl #25129] IO Buffer Test

2004-01-19 Thread Leopold Toetsch
Stefan Lidman <[EMAIL PROTECTED]> wrote: > readline S1, P1 The implementation of readline looks rather bogus. It allocates a huge (64K) string, sets that to zero, and the calls read, which calls readline. This is really suboptimal. It should probably call PIO_buf_readline or such directl

Re: [perl #25129] IO Buffer Test

2004-01-19 Thread Leopold Toetsch
Stefan Lidman <[EMAIL PROTECTED]> wrote: > This is a test for the buffer bug that > was discussed on p6i a few days ago. Thanks, fine. > output_is(<<'CODE', < set S0, "buffTest" > open P1, S0 open P1, S0, ">" I don't know, if it should even write the test file w/o tha

[perl #25129] IO Buffer Test

2004-01-19 Thread via RT
# New Ticket Created by Stefan Lidman # Please include the string: [perl #25129] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=25129 > Hello This is a test for the buffer bug that was discussed on p6i a few days ago. It