xdvi runtime error - part 2

2002-03-08 Thread Nicolae Santean
Continuing my attempts to run xdvi under cygwin, here are my success and new problem: I have fixed the problem with fcntl(F_SETOWN) - it actually is an option in the configuration file which allows to inhibit the use of this function. But xdvi still goes nuts and crashes after eating the entire

Re^3: xdvi runtime error

2002-03-07 Thread Nicolae Santean
You may be right. I was just looking to the memory eaten by the xdvi process as reported by the W2K's task manager. The crash was occurring at 128Mb of allocated memory, and now occurs at 256Mb. Thanks for this clarification, and thanks Corinna for the explanation about vfork(). I hope I will be

Re^2: xdvi runtime error

2002-03-07 Thread Randall R Schulz
Nicolae, At 07:15 2002-03-07, Nicolae Santean wrote: >Thanks for your replay/advice . Let me share with you what I have >found on my side: > >1. Apparently, the heap_chunk_in_mb registry does not always tweak >the memory default limit for cygwin. Many people report this issue >and it actually ha

Re: Re^2: xdvi runtime error

2002-03-07 Thread Corinna Vinschen
On Thu, Mar 07, 2002 at 10:15:06AM -0500, Nicolae Santean wrote: > 1. Apparently, the heap_chunk_in_mb registry does not always tweak > the memory default limit for cygwin. Many people report this issue > and it actually happened to me as well. But, here's what I tried: > increased the value to 51

Re^2: xdvi runtime error

2002-03-07 Thread Nicolae Santean
Thanks for your replay/advice . Let me share with you what I have found on my side: 1. Apparently, the heap_chunk_in_mb registry does not always tweak the memory default limit for cygwin. Many people report this issue and it actually happened to me as well. But, here's what I tried: increased th

Re: xdvi runtime error

2002-03-07 Thread Corinna Vinschen
On Wed, Mar 06, 2002 at 10:32:38PM -0500, Nicolae Santean wrote: > > I believe that the 128 megabyte realloc failure is a consequence > (memory leak - maybe) of the other errors: > > "xdvi: fcntl F_SETOWN: Invalid argument", "setsid: Not owner" > > I am getting these errors first, and then I wa

Re: xdvi runtime error

2002-03-06 Thread Nicolae Santean
I believe that the 128 megabyte realloc failure is a consequence (memory leak - maybe) of the other errors: "xdvi: fcntl F_SETOWN: Invalid argument", "setsid: Not owner" I am getting these errors first, and then I watch the memory being slowly flooded. By no means xdvi should go to 128Mb. I sus

Re: xdvi runtime error

2002-03-06 Thread Randall R Schulz
Nicolae, A 128 megabyte realloc fails? No kidding?? There is a Cygwin-wide allocation limit that defaults, if I recall correctly, to 128 megabytes. There is a registry entry that overrides this default called HEAP_CHUNK_IN_MB. Here are the details, excerpted from an email by "Scott A. Hill"

xdvi runtime error

2002-03-06 Thread Nicolae Santean
Hello, I have recently compiled xdvi22.53 under cygwin1.3.9, but I am having problems running it. The runtime error is: xdvi: fcntl F_SETOWN: Invalid argument - mktexpk --mfmode cx --bdpi 300 --mag 'magstep(0.5)' --dpi 329 cmsl10 '>&3' setsid: Not owner xdvi: fcntl F_SETOWN: Invalid argument xd