Enforcer hits ?

[Flype]

When i do this :

Code: Select all

a$ = "pure"
PokeS(@a$,"purebasic")
Debug a$

Here, i write illegaly to memory.

Does exists a tool that can monitor illegal writes to memory ?

[Trond]

The debugger will complain if you write outside the allocated string buffer.

[freak]

Only if the memory area after your allocated buffer is marked as invalid or readonly.
Usually small buffer overflows are not catched, because the remainder of the
memory page where your buffer is located is not marked invalid, and therefore
produces no error when written to.

[thefool]

Buffer overrides

[Flype]

@freak
thanx for the explanation.
how to declare such memory areas as invalid ?

and a tool ? a microsoft one perhaps...

[Fred]

A good way on Windows is to use HeapValidate() to help tracking down such bug. It's not easy if the overflow is only 1 byte for example, as Windows always reserve by block of 16 bytes. So writting after won't produce anything wrong.

[Flype]

fred, let's have fun :

( from AWEAR, french forum )

Code: Select all

PokeS(@"true", PeekS(@"false"))
x$ = "true"
Debug x$
Debug "true"

I don't think it's a bug, it seems normal but surprising me first time.

[Fred]

you writting directly in the data section, no wonder