Search

Cannot inspect local variables while debugging in VS2010. CXX0017 "Symbol not found" error by EV Group Software Department

Closed
as Fixed Help for as Fixed

17
0
Sign in
to vote
Type: Bug
ID: 613569
Opened: 10/14/2010 6:25:39 AM
Access Restriction: Public
3
Workaround(s)
15
User(s) can reproduce this bug
Hi,



We have following problem:

#include <atlstr.h>
#include <math.h>
int _tmain(int argc, _TCHAR* argv[])
{
    float f = 123.0;

    if(false)
    {
        CString str1;
    }
    else
    {
        CString str2;
        int a = 123;
        a++;
        a = sin(1.2*a);
        _tprintf(_T("%d"), a);
    }
    return 0;
}

Put breakpoint on a line with "a++;", start debugging and try to inspect variable "a". You will get "Symbol 'a' not found" error.

CXX0017: Error: symbol " a" not found.

Tested under Windows 7 Enterprise x64 and Windows XP Pro, Visual Studio 2010 Professional, Win32 Console Application project, Debug build.

Refer to:

http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/d9afcd67-6f98-4754-af0e-ed75c051615f/


Thanks,

Matthias
Details (expand)

Visual Studio/Silverlight/Tooling version

Visual Studio 2010

What category (if any) best represents this feedback?

Reliability

Steps to reproduce

#include <atlstr.h>
#include <math.h>
int _tmain(int argc, _TCHAR* argv[])
{
float f = 123.0;

if(false)
{
CString str1;
}
else
{
CString str2;
int a = 123;
a++;
a = sin(1.2*a);
_tprintf(_T("%d"), a);
}
return 0;
}

Put breakpoint on a line with "a++;", start debugging and try to inspect variable "a". You will get "Symbol 'a' not found" error.
CXX0017: Error: symbol " a" not found.

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

You will get "Symbol 'a' not found" error.
CXX0017: Error: symbol " a" not found.

Expected results

Watching the value of variable 'a' ;)
File Attachments
0 attachments
Sign in to post a comment.
Posted by Samuel T. Haven on 5/17/2012 at 9:42 PM
Well, this bug is known for almost 1 and a half year ... and there is still no fix for it. I've VS 2010 including SP1 and can absolutely second that bugreport!
Posted by datanewb on 3/30/2011 at 3:51 PM
I'm actually having this problem as well. I'm current on all of the updates and running windows 7. I'm wondering if I should try a fresh install of VS2010 or if an Add-on is to blame???
Posted by the_steiny on 2/10/2011 at 7:34 PM
Still no word on the hotfix? Are you freaking serious?!

I just tried out SP1 Beta and it fixed some of the problems but not all of them.

MS: At least let us know how to get the hotfix.
Posted by Castorix on 1/25/2011 at 11:39 AM
This *** very annoying*** bug is always unsolved :-(
Posted by Guglielmo Calligaro on 12/21/2010 at 7:36 AM
Same problem here ... YongKang Zhu , where are you?
Posted by mahendrent on 12/13/2010 at 1:42 AM
Any response from Microsoft?
We're also looking for the hotfix.
Visual Studio Debugging is pointless with this problem - have to resort to TRACE!
Posted by tom_mai78101 on 12/10/2010 at 2:53 AM
I can't find the hotfix as of now in the Downloads page.

Do you suppose the hotfix is included in Visual Studio 2010 Service Pack 1 beta? (Some Microsoft VC++ team mentioned this hotfix will be in a "new release"...)
Posted by brkicz on 12/9/2010 at 3:40 AM
Where is the hotfix?
Posted by EV Group Software Department on 12/1/2010 at 2:40 AM
It's pathetic!

Searched again for 1 hour at microsoft connect...

Why is the bug state set to fixed when nobody cares about publishing a hotfix?

Currently we're not able to debug our c++ projects!

We've to create local debug variables almost everywhere to debug certain state variables.

Thx to MS for its selfless efforts!
Posted by Keith-in-LosAltos on 11/21/2010 at 12:44 PM
Still looking for hotfix for this problem -- don't see it in:
http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Hotfix,Visual%20Studio%202010
Posted by thomasmcleod on 11/18/2010 at 9:51 PM
Looking for that hotfix. Regression test later.
Posted by EV Group Software Department on 11/16/2010 at 12:16 AM
Is there already a hotfix released ? And where could i download it?
Posted by chinaski on 11/10/2010 at 5:54 AM
From where to get this hotfix ?
Posted by Microsoft on 10/27/2010 at 10:49 AM
The problem has been known to us. We have found the root cause and fixed the problem. A hotfix will be released for VS 2010.

Thank you for taking the time to report this bug.

YongKang Zhu
--
VC++ CodeGen and Tools
Posted by Microsoft on 10/14/2010 at 6:45 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by 后排男生 on 12/18/2010 at 5:20 AM
i mean solving waitting problems of users, M$ can change it's label from 'hotfix' to 'coldfix'.
Posted by paulymath on 3/1/2012 at 10:24 AM
Try fully qualifying the variables that don't work with their namespace in the watch window. (not g_VisualStudioSucks but instead TrueStatements::g_VisualStudioSucks). This worked for me in VS 2008.
Posted by paulymath on 3/1/2012 at 10:47 AM
I should clarify that the above workaround only helps sometimes, and is only for the Watch window. For mouse-over inspection you're as screwed as before. Such crappy tools :\