🚀 go-pugleaf

What that means is somewhere in "your" part of the program you
are writing to a memory location outside your allocated space.
In your case, you are writing to memory location 0x0000:0x0000.
This would happen most of the time when the programmer uses
malloc() family of routines, doesn't care to check if
the allocation was successful and just goes ahead and uses
the pointer returned.

Microsoft compiler adds a piece of code at the "exit" of your
program which checks if this memory location is overwritten.
This is rather a clever way to partially check the misbehaviour
of a program.

What all this means is that you need to go back and debug your
program more carefully. Look for memcpy(), strcpy() kind of
routines in particular.

Another way it to put exit() after each phase of your program
and see when the messaage appears again. This way you can
narrow down your search.

Hope this helps.

Pradeep
tpradeep@cs.tamu.edu