I always assumed these were for C++ only but you are correct that there are symbols for the managed assemblies too.
I believe that you don't have to copy them anywhere - you just have to tell Visual Studio where to look for them. Tool/Options/Debugging/Symbols. I'm not sure if you can specify the root directory or if you have to specify each sub directory yourself. The C++ guys do this much more than I so hopefully one of them will pop in - its been a long time since I did this.
Yeah, it is a seperate download. But I don't have an option of where to specify the directory for symbols... I go to Tools/Options/Debugging, but no option for symbol directories. I am using VS2003.
I am just a bit frustrated debugging MDX, it usually give me some generic error, but the fact that I forgot to have BeginRender called is never an error... just some general error... or even better, a crash.
Does anyone know of how to setup DX9 and MDX and VS2003 to get the most amount of information on DX errors Thank you all.
Yeah, I crancked everything up and I still get a simple errors, nothing as nice as .NET has made me accustomed to. Oh well. Thank you for your input. I just hoped that the Symbol files would point me to the errors within the MDX files.
I developed my MDX wrapper in a seperate assembly and enabled debugging there. But, I did not enable the unmanagged debugging in my test app. I assumed the error would have been thrown by the wrapper assembly so it would debug it but I was wrong. Thank you, your info forced me to double check and it worked...
The best way to get debug output is to go into control panel and enable the debug versions of DirectX. Crank the debug output up to full.
Then set your project to 'enable unmanaged debugging' in the project settings. Then watch the output window. Things will be much slower but you may find your error that way.
Seems like there should be a symbols option in VS03 however its not in my VS03 either search for 'Specify a Symbol Path' in the help file and it tells you there should be one. I'm not sure why its not showing up for either of us.
MDX, where do I put the symbol files?
g0nzo
Well I didn't have that directory, but after a little hunting I discovered that its a separate download.
http://www.microsoft.com/downloads/details.aspx familyid=562D72FC-61C8-41A3-8BFF-509466F3D6AA
I always assumed these were for C++ only but you are correct that there are symbols for the managed assemblies too.
I believe that you don't have to copy them anywhere - you just have to tell Visual Studio where to look for them. Tool/Options/Debugging/Symbols. I'm not sure if you can specify the root directory or if you have to specify each sub directory yourself. The C++ guys do this much more than I so hopefully one of them will pop in - its been a long time since I did this.
ShozQ
Yeah, it is a seperate download. But I don't have an option of where to specify the directory for symbols... I go to Tools/Options/Debugging, but no option for symbol directories. I am using VS2003.
I am just a bit frustrated debugging MDX, it usually give me some generic error, but the fact that I forgot to have BeginRender called is never an error... just some general error... or even better, a crash.
Does anyone know of how to setup DX9 and MDX and VS2003 to get the most amount of information on DX errors Thank you all.
Ehsan Tabari
Its not a bug, its a feature! He he.
Yeah, I crancked everything up and I still get a simple errors, nothing as nice as .NET has made me accustomed to. Oh well. Thank you for your input. I just hoped that the Symbol files would point me to the errors within the MDX files.
Ok, thanks.
Mai Sy
Bruce Lee
Argghhh, I found what I did wrong.
I developed my MDX wrapper in a seperate assembly and enabled debugging there. But, I did not enable the unmanagged debugging in my test app. I assumed the error would have been thrown by the wrapper assembly so it would debug it but I was wrong. Thank you, your info forced me to double check and it worked...
Rutger van der Vleuten
stchong
The best way to get debug output is to go into control panel and enable the debug versions of DirectX. Crank the debug output up to full.
Then set your project to 'enable unmanaged debugging' in the project settings. Then watch the output window. Things will be much slower but you may find your error that way.
Seems like there should be a symbols option in VS03 however its not in my VS03 either search for 'Specify a Symbol Path' in the help file and it tells you there should be one. I'm not sure why its not showing up for either of us.