Re: Error VB 6

On Tue, 30 Aug 2005 22:10:23 -0700, Roy Lewallen <w7el@xxxxxxxxx>
wrote:

>VitorEugenio wrote:
>> I'm having a very strange problem in VB6.
>>
>> It only occur when I use the .exe file, while I'm debugging nothing
>> happens.
>>
>> The problem is that when the user closes the program appears an error
>> message like this:
>>
>> ----------
>> "a instrução no "0x012b02bf" fez referência à memória no
>> "0xb8012b02". A memória não pôde ser "written".
>>
>> Clique 'OK' para encerrar o programa"
>> ----------
>>
>> it's in portuguese because of my O.S. Its something like an instruction
>> refering to some memory, and It could not be written.
>>
>> does anybody already have this kind of problem? Know how to fix??
>>
>> tnks, Vitor Eugenio.
>
>I've seen this quite often, too. In English, it says:
>
>The instruction at "0x52604323" [for example] referenced memory at
>"0x00000040". The memory could not be 'read'.
>
>A note I wrote shows that the title bar said "vsmon.exe - application
>error" but I believe I've seen other applications in the title bar.
>
>Does anyone know what causes this?
>
Well, it can happen to anything really. I have seen that error come up
in various applications. My theory is that it usually refers to an
application trying to reference an unloaded object, or freed memory.
In fact, i've seen this a few times from various applications and i'm
even surer that i have produced this error myself a few times. :-)

It's probably not that hard to do it.

Declare a global, call it zap.
Allocate 10 global bytes to it.
Settimer(h, id, 2000, timerproc)
free(zap)
go into message loop

timerproc(blabla)
{
char ch = *zap;
}

Reckon that might just do it..

--

Regards, Frank
.

Relevant Pages

  • In Java
    ... objects for creating memory than static? ... method is used for Applications. ... How can I show my text in the status Bar in Applet and how can i ...
    (comp.lang.java.help)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... If the toolkit being used is not one of those, then it is irrelevant that some provide a means to do so, particularly if the "some" are not available for the platform being targeted. ... Not enough context for most real-world applications to recover at this point. ... At this point g_malloccalling abortbecomes a moot point, particularly if your auto-save code is robust against memory allocation errors. ...
    (comp.lang.c)
  • Re: ProDOS Plus
    ... operating system was not considered worth the problems when it was just as easy to make the applications support 128k or more ram. ... your suggested P-code system could do something similar by running in the aux 64k memory range $D000...FFFF or perhaps the aux ram used by the P8 /ram driver code space. ... the OS could fit in *only* the space that ProDOS now occupies. ... if practicality were a concern we probably wouldn't be using old hardware. ...
    (comp.sys.apple2)
  • Re: xmalloc string functions
    ... If these were the only choices (crashing applications or a frozen ... trying to malloc some rediculously large amount of memory - e.g. in the ... because their malloc wrapper decided to exit. ... Exiting on malloc failure makes sense for a utility like sort. ...
    (comp.lang.c)
  • Re: xmalloc string functions
    ... require memory allocations depending on the way the system works. ... Not enough context for most real-world applications to ... It is /more/ reliable to routinely auto-save the user's work (as you ... particularly if your auto-save code is robust against memory allocation ...
    (comp.lang.c)
Loading