Mail Archives: djgpp-workers/2012/07/31/13:26:48
On 07/31/2012 03:54 PM, Rugxulo wrote:
>> I think that one of suspects is nmalloc used instead of DJGPP own memory
>> allocation (as DJGPP free() is too slow). I had some stability problems
>> earlier running my own test program (linked with nmalloc) which allocates
>> large numbers of random memory blocks and after that frees them in random
>> order. That memory allocation test program caused random NTVDM crashes
>> on Windows Vista.
>
> It could be nmalloc's bug, who knows, but I don't trust Vista as far
> as I can throw it re: DPMI. I would not put it past them as their bug,
> even with the DPMI limit override. Seriously. Try testing in pure DOS,
> if possible, and see if it's still buggy.
Maybe. Similar problems does not happen using DJGPP own memory allocation
as far as I remember.
Well I do not have any pure DOS installation. Also Windows 7 Pro 64 bit version
is not suitable (maybe it is still possible to try WinXP compatibility mode,
really WinXP virtual machine provided by M$)
>
>> Not much testing done with built GCC snapshot though. Built GMP-5.0.5, but
>> one of
>> test-suite programs (mpz/t-io_raw.exe) failed. I did not have time
>> to study why it fails yet.
>
> Needs setmode(O_BINARY) ???
>
Highly unlikely as it build and tests runs OK when built with released
GCC versions I have tested.
Andris
- Raw text -