debugging 64 bit apps

[Michael Makuch]

I am using VS2005 to build my unmanaged c++ application. I recently
installed the Win SDK and now am making 64 bit builds and am attempting
to debug the 64 bit executable.

I am seeing strange behavior while debugging 64 bit binary with VS2005.
This is a "native" or unmanaged application. No .Net, no CLR.

When debugging the 64 bit executable many of the programs variables are
*not* displayed in auto or local debug windows. Quick Watch on them says
"symbol not found" or "expression cannot be evaluated". Mouse hover
over the variables shows no tip window at all. *Some* variables do
display correctly, and some do not.

I'm searching through the MS docs about this but have not found it.
What am I missing?

I see this running VS2005 both on 32 bit XP (remote debugging to a
Vista64 hosted app) as well as locally on 64 bit Vista.

As expected when I debug the 32 bit build of the same app all the
the variables display as always in Autos,Locals, Quick Watch,
mouse over variable hover etc.


Thanks
Mike

[David Lowndes]

Post by Michael Makuch
When debugging the 64 bit executable many of the programs variables are
*not* displayed in auto or local debug windows. Quick Watch on them says
"symbol not found" or "expression cannot be evaluated". Mouse hover
over the variables shows no tip window at all. *Some* variables do
display correctly, and some do not.
I'm searching through the MS docs about this but have not found it.
What am I missing?

Mike,

Are you sure you're debugging with all optimisation disabled? What
you're seeing is typical behaviour when debugging an optimised build.

Dave

[Michael Makuch]

Post by David Lowndes
Mike,
Are you sure you're debugging with all optimisation disabled? What
you're seeing is typical behaviour when debugging an optimised build.
Dave

Yeah, my bad. For my debug I think I was losing track of the .pdb's. And
for debugging the release build I found these:

http://blogs.msdn.com/greggm/archive/2004/12/15/315673.aspx
http://blogs.msdn.com/greggm/archive/2006/01/23/516447.aspx

Thanks.