Debugging Shader programs

[Alexander]

I've been trying to debug a shader program ( .fx- file ) that is loaded by a
Direct3D program written in C#.
I've done all the procedures described in SDK help:
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described

Results:
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted


Can anybody help me ?

Thanks,
Alexander.

[cody]

shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded by a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[Alexander]

I'm using vs2003. Any idea?

Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded by a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[Christian Schiedermeier]

Start your programm without debugging, then attach to the process using
Debug...Processes...Attach.
Select Direct3D as program type.

Christian

Post by Alexander
I'm using vs2003. Any idea?
Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded
by
a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[Alexander]

Thank you! It works!

Alexander.

Post by Christian Schiedermeier
Start your programm without debugging, then attach to the process using
Debug...Processes...Attach.
Select Direct3D as program type.
Christian

Post by Alexander
I'm using vs2003. Any idea?
Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded
by
a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[travis_]

I have used shader debugging with C++ successfully for a few years on my home
machine with .NET 2003.

From this newsgroup, I gather that the shader debugger (for managed code)
does not work with .NET 2005?

I have both 2005 and 2003 installed on my work computer. I can't seem to
get the DX installer to install the DX extensions for both versions.
Whenever I run the DX installer, it only seems to add the shader debugger to
2005. Does anyone know of a way to force the installer to put it on both?

Thanks!

Post by Alexander
Thank you! It works!
Alexander.

Post by Christian Schiedermeier
Start your programm without debugging, then attach to the process using
Debug...Processes...Attach.
Select Direct3D as program type.
Christian

Post by Alexander
I'm using vs2003. Any idea?
Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded
by
a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[legalize+ (Richard [Microsoft Direct3D MVP])]

[Please do not mail me a copy of your followup]

Post by travis_
I have used shader debugging with C++ successfully for a few years on my home
machine with .NET 2003.
From this newsgroup, I gather that the shader debugger (for managed code)
does not work with .NET 2005?

The shader debugger is only supported in VS.NET 2003; it shouldn't add
it to 2005.

The shader debugger has been deprecated and they now recommend that
you use the PIX tool in the most recent SDK for debugging shaders.

[travis_]

I can understand why MS would want to move the shader debugger functionality
into PIX but it would really be nice to not *lose* functionality while that
process is occuring.

Thank you for your assistance. Unfortunately, I'm still running into
trouble. I installed the August SDK (and uninstalled the previous SDK). Now
the shader debugger works with 2003. Unfortunately, I ran into a slew of
problems with PIX.

Here are some of the problems:
Crash immediately on startup when launching PIX using single frame capture
with C++ BasicHLSL sample.
Crash when attempting to pixel shader debug from PIX using single frame
capture with C# BasicHLSL_2005 sample (managed DX 2.0.50727).
Crash when attempting to pixel shader debug from PIX using single frame
capture with my app (C# managed DX 1.1.4322).

I don't know if it matters but the gpu i'm using is the ATI x600.

Has anyone seen anything like this? I'm suspecting install problems (since
all MS products now days seem to be extremely problematic in this area now).
This would mean installing everything from clean (yuck). Although I didn't
do anything unusual during the install and I don't have anything unusual on
my system (no WinFX beta, etc).

All I can say is I can't wait to get back to C++ and away from all of the
problems I've had since moving to managed code. I hope others have had a
better experience.

Post by legalize+ (Richard [Microsoft Direct3D MVP])
[Please do not mail me a copy of your followup]

Post by travis_
I have used shader debugging with C++ successfully for a few years on my home
machine with .NET 2003.
From this newsgroup, I gather that the shader debugger (for managed code)
does not work with .NET 2005?

The shader debugger is only supported in VS.NET 2003; it shouldn't add
it to 2005.
The shader debugger has been deprecated and they now recommend that
you use the PIX tool in the most recent SDK for debugging shaders.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Pilgrimage 2006, Saturday September 23rd: <http://pilgrimage.scene.org>
North America's Longest Running Demoparty

[legalize+ (Richard [Microsoft Direct3D MVP])]

[Please do not mail me a copy of your followup]

Post by travis_
I can understand why MS would want to move the shader debugger functionality
into PIX but it would really be nice to not *lose* functionality while that
process is occuring.

While I agree, MS doesn't work for me and I don't work for MS, so...

Post by travis_
Thank you for your assistance. Unfortunately, I'm still running into
trouble. I installed the August SDK (and uninstalled the previous SDK). Now
the shader debugger works with 2003. Unfortunately, I ran into a slew of
problems with PIX.

I would report those to ***@microsoft.com so that they can get
fixed.

Post by travis_
Has anyone seen anything like this? I'm suspecting install problems (since
all MS products now days seem to be extremely problematic in this area now).

I doubt its the install.

Post by travis_
All I can say is I can't wait to get back to C++ and away from all of the
problems I've had since moving to managed code. I hope others have had a
better experience.

I expect that this will only be a strategy that pays off in the short
term. Longer term I see things moving more into managed code and the
unmanaged path being less featureful.

The design-time support in the managed world is something that I
really like and it doesn't mesh well with unmanaged code.

[supoch14]

Post by legalize+ (Richard [Microsoft Direct3D MVP])
[Please do not mail me a copy of your followup]

Post by travis_
I can understand why MS would want to move the shader debugger functionality
into PIX but it would really be nice to not *lose* functionality while that
process is occuring.

While I agree, MS doesn't work for me and I don't work for MS, so...

Post by travis_
Thank you for your assistance. Unfortunately, I'm still running into
trouble. I installed the August SDK (and uninstalled the previous SDK). Now
the shader debugger works with 2003. Unfortunately, I ran into a slew of
problems with PIX.

fixed.

Post by travis_
Has anyone seen anything like this? I'm suspecting install problems (since
all MS products now days seem to be extremely problematic in this area now).

I doubt its the install.

Post by travis_
All I can say is I can't wait to get back to C++ and away from all of the
problems I've had since moving to managed code. I hope others have had a
better experience.

I expect that this will only be a strategy that pays off in the short
term. Longer term I see things moving more into managed code and the
unmanaged path being less featureful.
The design-time support in the managed world is something that I
really like and it doesn't mesh well with unmanaged code.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Pilgrimage 2006, Saturday September 23rd: <http://pilgrimage.scene.org>
North America's Longest Running Demoparty

[supoch14]

Post by travis_
I can understand why MS would want to move the shader debugger functionality
into PIX but it would really be nice to not *lose* functionality while that
process is occuring.
Thank you for your assistance. Unfortunately, I'm still running into
trouble. I installed the August SDK (and uninstalled the previous SDK). Now
the shader debugger works with 2003. Unfortunately, I ran into a slew of
problems with PIX.
Crash immediately on startup when launching PIX using single frame capture
with C++ BasicHLSL sample.
Crash when attempting to pixel shader debug from PIX using single frame
capture with C# BasicHLSL_2005 sample (managed DX 2.0.50727).
Crash when attempting to pixel shader debug from PIX using single frame
capture with my app (C# managed DX 1.1.4322).
I don't know if it matters but the gpu i'm using is the ATI x600.
Has anyone seen anything like this? I'm suspecting install problems (since
all MS products now days seem to be extremely problematic in this area now).
This would mean installing everything from clean (yuck). Although I didn't
do anything unusual during the install and I don't have anything unusual on
my system (no WinFX beta, etc).
All I can say is I can't wait to get back to C++ and away from all of the
problems I've had since moving to managed code. I hope others have had a
better experience.

Post by legalize+ (Richard [Microsoft Direct3D MVP])
[Please do not mail me a copy of your followup]

Post by travis_
I have used shader debugging with C++ successfully for a few years on my home
machine with .NET 2003.
From this newsgroup, I gather that the shader debugger (for managed code)
does not work with .NET 2005?

The shader debugger is only supported in VS.NET 2003; it shouldn't add
it to 2005.
The shader debugger has been deprecated and they now recommend that
you use the PIX tool in the most recent SDK for debugging shaders.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Pilgrimage 2006, Saturday September 23rd: <http://pilgrimage.scene.org>
North America's Longest Running Demoparty

[supoch14]

Post by legalize+ (Richard [Microsoft Direct3D MVP])
[Please do not mail me a copy of your followup]

Post by travis_
I have used shader debugging with C++ successfully for a few years on my home
machine with .NET 2003.
From this newsgroup, I gather that the shader debugger (for managed code)
does not work with .NET 2005?

The shader debugger is only supported in VS.NET 2003; it shouldn't add
it to 2005.
The shader debugger has been deprecated and they now recommend that
you use the PIX tool in the most recent SDK for debugging shaders.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Pilgrimage 2006, Saturday September 23rd: <http://pilgrimage.scene.org>
North America's Longest Running Demoparty

[supoch14]

Post by travis_
I have used shader debugging with C++ successfully for a few years on my home
machine with .NET 2003.
From this newsgroup, I gather that the shader debugger (for managed code)
does not work with .NET 2005?
I have both 2005 and 2003 installed on my work computer. I can't seem to
get the DX installer to install the DX extensions for both versions.
Whenever I run the DX installer, it only seems to add the shader debugger to
2005. Does anyone know of a way to force the installer to put it on both?
Thanks!

Post by Alexander
Thank you! It works!
Alexander.

Post by Christian Schiedermeier
Start your programm without debugging, then attach to the process using
Debug...Processes...Attach.
Select Direct3D as program type.
Christian

Post by Alexander
I'm using vs2003. Any idea?
Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded
by
a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any
symbols.
- When I try to launch the debugger from Debug|Direct3D the code will
only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[supoch14]

Post by Alexander
Thank you! It works!
Alexander.

Post by Christian Schiedermeier
Start your programm without debugging, then attach to the process using
Debug...Processes...Attach.
Select Direct3D as program type.
Christian

Post by Alexander
I'm using vs2003. Any idea?
Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded
by
a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[supoch14]

Post by Christian Schiedermeier
Start your programm without debugging, then attach to the process using
Debug...Processes...Attach.
Select Direct3D as program type.
Christian

Post by Alexander
I'm using vs2003. Any idea?
Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded
by
a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[supoch14]

Post by Alexander
I'm using vs2003. Any idea?
Alexander.

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded by a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[supoch14]

Post by cody
shader debugging works only in vs2003, but not (yet) in vs2005.

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded by a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.

[supoch14]

Post by Alexander
I've been trying to debug a shader program ( .fx- file ) that is loaded by a
Direct3D program written in C#.
- inserting DX extensions
- Enable Debug mode from the control panel
- setting needed flags as described
- When I start the application then the breakpoint within the shader is
never reached and I get the message that there are not loaded any symbols.
- When I try to launch the debugger from Debug|Direct3D the code will only
be compiled but not be executed
- Keyword of the shader code are highlighted
Can anybody help me ?
Thanks,
Alexander.