cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

Apostate
Journeyman III

gDEbugger crashing

I was using gDEbugger 5.8 with Catalyst 11.5 and found it incredibly useful.  I discovered there was a newer version (6.0) with integration in visual studio and figured I should try it to see if there are any new features I can use.  I only use it for debugging OpenGL.

I installed the new gDEBugger, but it seemed to refuse to recognize my ATI Mobility Radeon HD 4650.  I don't remember the exact message it was giving me, but it was pretty similar to this one from another post "The version of Catalyst you have installed does not contain support for this version of gDEBugger. Kernel debugging will be disabled. It is recommended to install the latest versions of both Catalyst and gDEBugger".  It would also give me no debug information for OpenGL.

I updated my drivers to Catalyst 11.8 and now both gDEbugger 5.8 and 6.0 started to crash.  5.8 would let me hit the pause button or a breakpoint, but would crash if I tried to open any of the viewer windows.  6.0 crashes as soon as I hit the pause button or a breakpoint.

I noticed another post saying there might be something needed in 11.7, so I uninstalled 11.8, ran driver sweeper to clean up any remaining files and installed 11.7, but I have the same exact problem as with 11.8.  Both gDEbuggers still crash.

 Number of platforms:     1
  Platform Profile:     FULL_PROFILE
  Platform Version:     OpenCL 1.1 AMD-APP-SDK-v2.5 (709.2)
  Platform Name:     AMD Accelerated Parallel Processing
  Platform Vendor:     Advanced Micro Devices, Inc.
  Platform Extensions:     cl_khr_icd cl_amd_event_callback cl_amd_offline_devices cl_khr_d3d10_sharing


  Platform Name:     AMD Accelerated Parallel Processing
Number of devices:     2
  Device Type:      CL_DEVICE_TYPE_GPU
  Device ID:      4098
  Max compute units:     8
  Max work items dimensions:    3
    Max work items[0]:     128
    Max work items[1]:     128
    Max work items[2]:     128
  Max work group size:     128
  Preferred vector width char:    16
  Preferred vector width short:    8
  Preferred vector width int:    4
  Preferred vector width long:    2
  Preferred vector width float:    4
  Preferred vector width double:   0
  Native vector width char:    16
  Native vector width short:    8
  Native vector width int:    4
  Native vector width long:    2
  Native vector width float:    4
  Native vector width double:    0
  Max clock frequency:     450Mhz
  Address bits:      32
  Max memory allocation:    134217728
  Image support:     No
  Max size of kernel argument:    1024
  Alignment (bits) of base address:   32768
  Minimum alignment (bytes) for any datatype:  128
  Single precision floating point capability
    Denorms:      No
    Quiet NaNs:      Yes
    Round to nearest even:    Yes
    Round to zero:     Yes
    Round to +ve and infinity:    Yes
    IEEE754-2008 fused multiply-add:   Yes
  Cache type:      None
  Cache line size:     0
  Cache size:      0
  Global memory size:     268435456
  Constant buffer size:     65536
  Max number of constant args:    8
  Local memory type:     Global
  Local memory size:     16384
  Kernel Preferred work group size multiple:  32
  Error correction support:    0
  Unified memory for Host and Device:   0
  Profiling timer resolution:    1
  Device endianess:     Little
  Available:      Yes
  Compiler available:     Yes
  Execution capabilities:    
    Execute OpenCL kernels:    Yes
    Execute native function:    No
  Queue properties:    
    Out-of-Order:     No
    Profiling :      Yes
  Platform ID:      000007FEE79FD348
  Name:       ATI RV730
  Vendor:      Advanced Micro Devices, Inc.
  Device OpenCL C version:    OpenCL C 1.0
  Driver version:     CAL 1.4.1457
  Profile:      FULL_PROFILE
  Version:      OpenCL 1.0 AMD-APP-SDK-v2.5 (709.2)
  Extensions:      cl_khr_gl_sharing cl_amd_device_attribute_query cl_khr_d3d10_sharing


  Device Type:      CL_DEVICE_TYPE_CPU
  Device ID:      4098
  Max compute units:     2
  Max work items dimensions:    3
    Max work items[0]:     1024
    Max work items[1]:     1024
    Max work items[2]:     1024
  Max work group size:     1024
  Preferred vector width char:    16
  Preferred vector width short:    8
  Preferred vector width int:    4
  Preferred vector width long:    2
  Preferred vector width float:    4
  Preferred vector width double:   0
  Native vector width char:    16
  Native vector width short:    8
  Native vector width int:    4
  Native vector width long:    2
  Native vector width float:    4
  Native vector width double:    0
  Max clock frequency:     2194Mhz
  Address bits:      64
  Max memory allocation:    2147483648
  Image support:     Yes
  Max number of images read arguments:   128
  Max number of images write arguments:   8
  Max image 2D width:     8192
  Max image 2D height:     8192
  Max image 3D width:     2048
  Max image 3D height:     2048
  Max image 3D depth:     2048
  Max samplers within kernel:    16
  Max size of kernel argument:    4096
  Alignment (bits) of base address:   1024
  Minimum alignment (bytes) for any datatype:  128
  Single precision floating point capability
    Denorms:      Yes
    Quiet NaNs:      Yes
    Round to nearest even:    Yes
    Round to zero:     Yes
    Round to +ve and infinity:    Yes
    IEEE754-2008 fused multiply-add:   No
  Cache type:      Read/Write
  Cache line size:     64
  Cache size:      32768
  Global memory size:     4260388864
  Constant buffer size:     65536
  Max number of constant args:    8
  Local memory type:     Global
  Local memory size:     32768
  Kernel Preferred work group size multiple:  1
  Error correction support:    0
  Unified memory for Host and Device:   1
  Profiling timer resolution:    466
  Device endianess:     Little
  Available:      Yes
  Compiler available:     Yes
  Execution capabilities:    
    Execute OpenCL kernels:    Yes
    Execute native function:    Yes
  Queue properties:    
    Out-of-Order:     No
    Profiling :      Yes
  Platform ID:      000007FEE79FD348
  Name:       Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz
  Vendor:      GenuineIntel
  Device OpenCL C version:    OpenCL C 1.1
  Driver version:     2.0
  Profile:      FULL_PROFILE
  Version:      OpenCL 1.1 AMD-APP-SDK-v2.5 (709.2)
  Extensions:      cl_khr_fp64 cl_amd_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_byte_addressable_store cl_khr_gl_sharing cl_ext_device_fission cl_amd_device_attribute_query cl_amd_vec3 cl_amd_media_ops cl_amd_popcnt cl_amd_printf cl_khr_d3d10_sharing

0 Likes
10 Replies

When the system crashed did the "Send crash report" dialog appeared and did you use it to send the crash log?

You can send that information so we can get more data to understand the problem, or you can post here the information and the logs (from 5.8 and/or 6.0).

0 Likes

I did report the crash log several times, but here's the one from 5.8:

Call stack:
Function name - File path - Line number - Module path - Function Start address - Instruction counter address
suBreakpointsManager::triggerBreakpointException - q:\workspaces\grspiesutilities\src\subreakpointsmanager.cpp - 427 - c:\program files (x86)\graphic remedy\gdebugger\GRSpiesUtilities.dll - 0x00215da0 - 0x00215e1b
suBreakpointsManager::testAndTriggerBeforeFuncExecutionBreakpoints - q:\workspaces\grspiesutilities\src\subreakpointsmanager.cpp - 355 - c:\program files (x86)\graphic remedy\gdebugger\GRSpiesUtilities.dll - 0x00215c80 - 0x00215cdf
gsOpenGLMonitor::testAndTriggerBeforeFuncExecutionBreakpoints - q:\workspaces\gropenglservers\src\gsopenglmonitor.cpp - 1489 - c:\program files (x86)\graphic remedy\gdebugger\spies\OPENGL32.dll - 0x1008bba0 - 0x1008bc76
gsOpenGLMonitor::addFunctionCall - q:\workspaces\gropenglservers\src\gsopenglmonitor.cpp - 1038 - c:\program files (x86)\graphic remedy\gdebugger\spies\OPENGL32.dll - 0x1008d1a0 - 0x1008d264
glDrawElements - q:\workspaces\gropenglservers\src\gsopenglwrappers.cpp - 1401 - c:\program files (x86)\graphic remedy\gdebugger\spies\OPENGL32.dll - 0x100904b0 - 0x100904e6
MeshObject::render - d:\coding\enginegit\engine\src\meshobject.cpp - 78 - D:\Coding\EngineGit\Debug\Engine.exe - 0x016534a0 - 0x01653535
MeshNode::render - d:\coding\enginegit\engine\src\meshnode.cpp - 99 - D:\Coding\EngineGit\Debug\Engine.exe - 0x0164dc60 - 0x0164dcfd
MeshNode::render - d:\coding\enginegit\engine\src\meshnode.cpp - 105 - D:\Coding\EngineGit\Debug\Engine.exe - 0x0164dc60 - 0x0164dd42
Mesh::render - d:\coding\enginegit\engine\src\mesh.cpp - 59 - D:\Coding\EngineGit\Debug\Engine.exe - 0x0164b450 - 0x0164b5fb
Body::render - d:\coding\enginegit\engine\src\body.cpp - 26 - D:\Coding\EngineGit\Debug\Engine.exe - 0x0162d940 - 0x0162d97d
Object::render - d:\coding\enginegit\engine\src\object.cpp - 50 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01653bd0 - 0x01653c54
ObjectMgr::render - d:\coding\enginegit\engine\src\objectmgr.cpp - 36 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01654380 - 0x016543da
GameGlobals::render3d - d:\coding\enginegit\engine\src\gameglobals.cpp - 30 - D:\Coding\EngineGit\Debug\Engine.exe - 0x0163fc30 - 0x0163fc5a
RenderEngine::render3d - d:\coding\enginegit\engine\src\renderengine.cpp - 119 - D:\Coding\EngineGit\Debug\Engine.exe - 0x0165c9f0 - 0x0165caa9
RenderEngine::render - d:\coding\enginegit\engine\src\renderengine.cpp - 102 - D:\Coding\EngineGit\Debug\Engine.exe - 0x0165c910 - 0x0165c954
wWinMain - d:\coding\enginegit\engine\src\engine.cpp - 60 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01637ba0 - 0x01637cc7
__tmainCRTStartup - f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c - 547 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01d1b5a0 - 0x01d1b7dc
wWinMainCRTStartup - f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c - 370 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01d1b580 - 0x01d1b58e
BaseThreadInitThunk - N/A - N/A - C:\Windows\syswow64\kernel32.dll - 0x74a93388 - 0x74a93399
RtlInitializeExceptionChain - N/A - N/A - C:\Windows\system32\ntdll.dll - 0x772c9e6f - 0x772c9ed1

System DLL Versions:
 - atioglxx.dll: 6.14.10.10907
 - atio6axx.dll: 6.14.10.10907
 - aticfx32.dll: 8.17.10.1086
 - aticfx64.dll: 8.17.10.1086
 - aticaldd.dll: 6.14.10.1457
 - OpenCL.dll: 1.1.0.0

OpenGL Renderer:
 - Renderer Vendor: ATI Technologies Inc.
 - Renderer Name: ATI Mobility Radeon HD 4650
 - Renderer Version: 3.3.10907 Compatibility Profile Context
 - Renderer Type: Installable client

Device 1 (GPU):
 - Platform ID: 1
 - Device Type: GPU
 - Device Name: ATI RV730
 - Vendor: Advanced Micro Devices, Inc.

Device 2 (CPU):
 - Platform ID: 1
 - Device Type: CPU
 - Device Name: Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz
 - Vendor: GenuineIntel

Platform 1:
 - Vendor: Advanced Micro Devices, Inc.
 - Name: AMD Accelerated Parallel Processing
 - Profile: FULL_PROFILE
 - Version: OpenCL 1.1 AMD-APP-SDK-v2.5 (709.2)

And here is the one from 6.0:

Call stack:
Function name - File path - Line number - Module path - Function Start address - Instruction counter address
suBreakpointsManager::triggerBreakpointException - q:\workspaces\grspiesutilities\src\subreakpointsmanager.cpp - 664 - C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\gDEBugger\GRSpiesUtilities.dll - 0x5a316410 - 0x5a316494
suBreakpointsManager::testAndTriggerBeforeFuncExecutionBreakpoints - q:\workspaces\grspiesutilities\src\subreakpointsmanager.cpp - 588 - C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\gDEBugger\GRSpiesUtilities.dll - 0x5a3162c0 - 0x5a31632f
gsOpenGLMonitor::testAndTriggerBeforeFuncExecutionBreakpoints - q:\workspaces\gropenglservers\src\gsopenglmonitor.cpp - 1518 - C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\gDEBugger\spies\opengl32.dll - 0x5a3c6660 - 0x5a3c675f
gsOpenGLMonitor::addFunctionCall - q:\workspaces\gropenglservers\src\gsopenglmonitor.cpp - 1072 - C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\gDEBugger\spies\opengl32.dll - 0x5a3c7310 - 0x5a3c73e2
glClear - q:\workspaces\gropenglservers\src\gsopenglwrappers.cpp - 323 - C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\AMD\gDEBugger\spies\opengl32.dll - 0x5a3c84d0 - 0x5a3c84e8
RenderEngine::render - d:\coding\enginegit\engine\src\renderengine.cpp - 100 - D:\Coding\EngineGit\Debug\Engine.exe - 0x016bc910 - 0x016bc945
wWinMain - d:\coding\enginegit\engine\src\engine.cpp - 60 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01697ba0 - 0x01697cc7
__tmainCRTStartup - f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c - 547 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01d7b5a0 - 0x01d7b7dc
wWinMainCRTStartup - f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c - 370 - D:\Coding\EngineGit\Debug\Engine.exe - 0x01d7b580 - 0x01d7b58e
BaseThreadInitThunk - N/A - N/A - C:\Windows\SysWOW64\kernel32.dll - 0x74a93388 - 0x74a93399
RtlInitializeExceptionChain - N/A - N/A - C:\Windows\SysWOW64\ntdll.dll - 0x772c9e6f - 0x772c9ed1

System DLL Versions:
 - atioglxx.dll: 6.14.10.10907
 - atio6axx.dll: 6.14.10.10907
 - aticfx32.dll: 8.17.10.1086
 - aticfx64.dll: 8.17.10.1086
 - aticaldd.dll: 6.14.10.1457
 - OpenCL.dll: 1.1.0.0

OpenGL Renderer:
 - Renderer Vendor: ATI Technologies Inc.
 - Renderer Name: ATI Mobility Radeon HD 4650
 - Renderer Version: 3.3.10907 Compatibility Profile Context
 - Renderer Type: Installable client

Drivers versions:
 - CAL version: 1.4.1457
 - Catalyst version: 11.7

Device 1 (GPU):
 - Platform ID: 1
 - Device Type: GPU
 - Device Name: ATI RV730
 - Vendor: Advanced Micro Devices, Inc.

Device 2 (CPU):
 - Platform ID: 1
 - Device Type: CPU
 - Device Name: Intel(R) Core(TM)2 Duo CPU     T6600  @ 2.20GHz
 - Vendor: GenuineIntel

Platform 1:
 - Vendor: Advanced Micro Devices, Inc.
 - Name: AMD Accelerated Parallel Processing
 - Profile: FULL_PROFILE
 - Version: OpenCL 1.1 AMD-APP-SDK-v2.5 (709.2)

0 Likes

Private message was sent to you

0 Likes

I haven't seen a private message and it is saying I have no new private messages.  I checked to make sure private messages were turned on and they are, so not really sure why I haven't gotten anything.

0 Likes

Are there any news on this issue?

0 Likes

I am also facing the same problem. I have a Redwood and gdebugger keeps on crashing on my kernel. The Teapot sample works fine and can be debugged but none of my kernels work.

I also sent a bug report for this. 

Are there any known bugs. This is happening on a Win 7 64 bit.

0 Likes

On a different machine with a Cayman I see the following message.

The thread tried to read from or write to a virtual address to which it does not have access.

Any ideas ?

0 Likes

Just wanted to add, that i experience almost the same problem, except that in my case, gDEBugger crashes right after launching the debug process from withing it's menu. Normal debugging works OK. The report windowed shows up and i pressed the "Send" button. After that, VS crashes.

I got Win 7 (x86), AMD 6870,  Cat. 11.8, VS 2010 (SP1).

0 Likes

I still haven't gotten the private message you mentioned.  If you want to try emailing me instead, my address is zombie.apostate at gmail.

0 Likes

Any progress figuring out the problem?

0 Likes