Re: Access violation after nullifiying and again allocating pointer

Thanks for your answer, Jan !

Now I have checked the runtime error, which appears when allocating the pointer array, where the proramm crashes. It is runtime error 41 - which means that there is not enough virtual memory.
But it appears if I replace the nullify with a deallocate, too.

Klemens

Jan Vorbrüggen wrote: 
You should be aware that nullifying the pointer does _not_ deallocate
the memory that now, possibly, has become inaccessible to the program.
Of course, a deallocate also nullifies the pointer. So, perhaps you
program is running out of memory, and VF 5's RTL is unkind in just
crashing instead of providing a useful error message?

BTW, VF 5 is....well...old. Why not use, for instance, the non-commercial
license for the Intel compiler? There was some strange wording in that
license recently with regard to academic, though...

Jan 
.

Relevant Pages

  • RE: run time errors?
    ... > An error that occurs during the execution of a program. ... For example, running out of memory ... that would be a runtime error. ... Examples of compile-time errors are syntax errors ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Runtime error during Fritz analysis
    ... It's the memory deficiency. ... game I played with CM9K and cleaned up and saved as a PGN file. ... the runtime error. ... 256mb is very low for a pc running fritz9. ...
    (rec.games.chess.computer)
  • Problems running self-building code with Unicode
    ... I have an app developed with C++ and inline assembly, ... The memory where the code is built is allocated with VirtualAlloc ... It works in Unicode Release ... "Runtime Error! ...
    (microsoft.public.win32.programmer.kernel)
  • Runtime Error R6025 + WMP 9 in Win98SE
    ... Everytime I try to acquire a license for my WMA files, ... Runtime Error! ... Program: C:\PROGRAM FILES\WINDOWS MEDIA PLAYER\WMPLAYER.EXE ...
    (microsoft.public.windowsmedia.player)
  • Re: Unloading a DLL WEP
    ... The problem is that I need it to release from memory when it is finished ... Are you talking about an ActiveX DLL? ... about a runtime error causing the DLL to "get stuck" in ram, ... use generous doses of error trapping so common runtime errors won't crash ...
    (microsoft.public.vb.general.discussion)