Detect Global Memory Access Violations about gpuocelot HOT 2 CLOSED

From [email protected] on July 10, 2009 08:11:00

Added a hook from the executive class to the emulated kernel class. This allows the
emulated kernel to inspect all registered memory allocations. Added checks to all
global memory accesses to determine whether an access falls within an allocated
region. Throws an exception if the area has not been allocated.

Most of the SDK examples pass with this modification. However, some do not. I need
to add better debugging information and step through these examples to determine if
they are really memory violations, or if there is some problem with not all allocated
regions appearing in the allocation table. A big problem here could be regions that
are mapped from OpenGL buffers...

Status: Started

from gpuocelot.

From [email protected] on July 11, 2009 02:35:51

Made the following changes:

1. Added hooks into openGL buffers to register sizes as well as the base of the buffer.

2. Added debugging messages that show the nearby regions to an access that does not
   fall within any mapped region.

3. Added macro to disable memory checking if required to avoid any performance overhead.

4. Added tracking of statically allocated global variables as well as regions created
   via device memory allocation (cudaMalloc).

This should fix this issue...

Status: Fixed

from gpuocelot.