Date:	Fri, 14 May 1993 02:23 EDT
From:	"Wonkoo Kim, EE, U. of Pittsburgh" <WKIM AT vms DOT cis DOT pitt DOT edu>
Subject:	Re: go32 ??
To:	sandmann AT clio DOT rice DOT EDU, djgpp AT sun DOT soe DOT clarkson DOT EDU
Cc:	fine AT main1 DOT jinr DOT dubna DOT SU

>From: sandmann AT clio DOT rice DOT EDU (Charles W. Sandmann)
>Subject: RE: go32 ??
>
>> In my feeling, go32 itself has some bug(?) in handling system() call.???
>
>There is one known bug in the paging routines (a patch was posted around
>January to this list) which causes memory to be corrupted after return from
>a system() call.  I don't know if this is your problem.  I have been using
>system() in many programs for about 9 months and have only seen a couple
>of occasional problems.

fine AT main1 DOT jinr DOT dubna DOT SU sent me a patch to paging.c (thanks).

I rebuilt go32 1.09 with the patch.  The situation became better in a side and 
worse in the other side.

System call to "dir" or "mem" worked after patching, but system call to 
"zcat.exe" still failed after some amount of memory had been allocated.
It was the same error as I reported before. 
(zcat.exe(from gzip.exe) is a MSC 5.1 compiled version.)

DOWN SIDE: 
Before go32 is patched, system("zcat file1 > file2") always worked regardless 
of file1 size if no memory was allocated after program started.  
After patching, the system() failed if file1 is big. 
(It worked for 16KB, 64KB, and failed for 256KB file.)
This new error is too critical to my program and so I have to return to the 
original go32 1.09.

Thus the patch to paging.c seems to be not good.  It's a patch making one good, 
but some other bad.  

Thanks.

Wonkoo.

- Raw text -