Archives Discussions

[maxbarraclough]

Trying to use the CodeXL (from Visual Studio) OpenCL debugging using breakpoints, I invariably get the message:

The thread tried to access an array element that is out of bounds and the underlying hardware supports bounds checking

even where the kernel is doing nothing but declaring a local int, assigning it a value, and then returning. I show this in the attached screenshots. All screenshots are based on AMD's 'Hello world' sample.

Sometimes Visual Studio crashes entirely after this error happens.

The error does not occur if I do not place breakpoints in OpenCL code. Also, 'ordinary' Visual Studio debugging (of C++ code) works fine.

Hardware:

Phenom II CPU, R9 280X graphics card ('Tahiti' architecture)

Software:

Windows 8.1 64 bit

Visual Studio 2010 Premium

APP SDK 2.9

CodeXL 1.4.5724

Catalyst drivers 14.4

I didn't get this issue using my old Radeon HD 6870. The 280X is a new card; I have reinstalled everything relevant: not only the Catalyst drivers, but also the APP SDK and CodeXL.

[dipak]

Hi,

As you mentioned, your code is running fine for following conditions:

1. Debugging using ordinary VSC++,

2. Debugging using CodeXL from VSC++ without any breakpoints

and is not working or crashing when

1. Debugging using CodeXL from VSC++ with breakpoints

So, may be it related to CodeXL itself. Please can you try to debug the same using only CodeXL (not from VSC++) and check whether you face similar problem or not.

FYI: For CodeXL related issue, there is a separate CodeXL Forum.

Regards,

[maxbarraclough]

Please can you try to debug the same using only CodeXL (not from VSC++) and check whether you face similar problem or not.

I tried adding a breakpoint to the Teapot sample bundled with CodeXL (standalone, not Visual Studio integrated). I saw a similar issue: things work fine when I don't add a breakpoint, but I see a crash if I do add one. Attached screenshots show this.

FYI: For CodeXL related issue, there is a separate CodeXL Forum.

Should I create a new thread there linking to this one, or can a moderator move this thread?

Thanks.

[pinform]

I shall move this thread to the CodeXL forum.

--Prasad

[zish]

I have the same issue - Any news on this?

System:

- HD7850

-Windows 7 x64

-Tried with the latest drivers and also with the beta drivers

Call-Stack (is always the same)

	0xffffffff()    C / C++
	aticaldd.dll!calddiGetVersion() + 1685376 bytes    C / C++
	aticaldd.dll!calddiGetVersion() + 1680159 bytes    C / C++
	aticaldd.dll!calddiGetVersion() + 27578 bytes    C / C++
	AMDOpenCLDebug.dll!0x0f148b90()    C / C++
	AMDOpenCLDebug.dll!0x0f146897()    C / C++
	AMDOpenCLDebug.dll!0x0f146b67()    C / C++
	AMDOpenCLDebug.dll!0x0f146e19()    C / C++
	AMDOpenCLDebug.dll!0x0f12933c()    C / C++
	AMDOpenCLDebug.dll!0x0f117fe2()    C / C++
	AMDOpenCLDebug.dll!0x0f1022f0()    C / C++
	AMDOpenCLDebug.dll!0x0f102b56()    C / C++
	amdocl.dll!clRetainSampler() + 27878 bytes    C / C++
	amdocl.dll!clRetainSampler() + 28133 bytes    C / C++
	amdocl.dll!clRetainSampler() + 11292 bytes    C / C++
	amdocl.dll!clRetainSampler() + 96299 bytes    C / C++
	kernel32.dll!BaseThreadInitThunk() + 17 bytes    C / C++
	ntdll.dll!RtlInitializeExceptionChain() + 98 bytes    C / C++

Reproducable with the standalone CodeXL application and with the Visual Studio plugin.

If more information is needed just ask - I really need a fix for this

[zish]

Dowgraded GPU driver to verision 13.9 (http://www2.ati.com/drivers/13-9_win7_win8_64_dd_ccc_whql.exe) which uses an older OpenCL driver.

=> Everything works fine

Still waiting for anything official...

[urishomroni · Accepted solution]

Hi,

According to the call stack in your crash report, this is a known issue caused by the progression of the compiler in the newest AMD Radeon drivers.

This issue will be fixed in the upcoming release of CodeXL (1.5).

If you have access to a driver before 14.4 (e.g., 14.1 or 13.9 like you noted), you may want to switch to using it until CodeXL 1.5 is released.

Sorry for the inconvenience,