Printable View
Alright, here is my piece of code :
I put a break point at the following instruction and when I look in the watch section of visual C++ 2010, I have that :Code:long *a = &(cgm.o->m_metafileVersion);
a = 0x053e3d50
&(cgm.o->m_metafileVersion) = 0x053e3d28
weird, isn't it?
Why? :confused:
Why it is weird?
because "a" is a pointer and it get the adresse of cgm.o->m_metafileVersion.... so unless I woke up in a parallel world, where the C++ rules would be different, "long *a" should be equal to "&(cgm.o->m_metafileVersion)"... and it's not (!!!)
:ehh:
When did you look in the watch section: before or after this line had been executed?
after! I put a break point at the following instruction.
yeah I know it's weird... but I don't even know, who can I speak to to get help...
I did a very simple test:Quote:
Originally Posted by ArnaudCas
What I see in the watch window is:Code:class CTest
{
public:
long m_metafileVersion;
CTest() {m_metafileVersion = 0;}
};
class CGm
{
public:
CTest o;
int something;
CGm() {something = 0;}
};
CGm cgm;
long *a = &(cgm.o.m_metafileVersion);
The only difference I see is: I use the object o while you use some pointer o.Code:&(cgm.o.m_metafileVersion) 0x0012f4a8 long *
a 0x0012f4a8 long *
Where does it point to?
errh, the object "o" points to a data structure, a class, from the library I use (it's a lib to read cgm files)
Do you think the lib has a problem? or my EDI (Visual Studio)?
I don't know.
I tested inQuote:
Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.0.30319 SP1Rel
Installed Version: Ultimate
....
Microsoft Visual C++ 2010 01019-532-2002102-70738
Microsoft Visual C++ 2010
....
Hotfix for Microsoft Visual Studio 2010 Ultimate - ENU (KB2548139) KB2548139
This hotfix is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2548139.
Hotfix for Microsoft Visual Studio 2010 Ultimate - ENU (KB2565057) KB2565057
This hotfix is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2565057.
Microsoft Visual Studio 2010 SharePoint Developer Tools 10.0.40219
Microsoft Visual Studio 2010 SharePoint Developer Tools
Microsoft Visual Studio 2010 Ultimate - ENU Service Pack 1 (KB983509) KB983509
This service pack is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/983509.
Security Update for Visual Studio 2010 Shell (Isolated) - ENU (KB2644980) KB2644980
This security update is for Visual Studio 2010 Shell (Isolated) - ENU.
If you later install a more recent service pack, this security update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2644980.
I dont see what I have to do with your links.
I tested the lib in a new simple main program, and I have the error too. So Maybe it comes from the lib, but how? The error seems to come from the IDE, nevertheless, right?
Just compare it with your VS2010 installation data.Quote:
Originally Posted by ArnaudCas
I don't know, sorry.Quote:
Originally Posted by ArnaudCas
what error ? we can have no idea if it is a program bug ( highly plausible ), a compiler bug ( highly unplausible ) or a debugger glitch by just looking at a single line of apparently correct code.Quote:
Originally Posted by ArnaudCas
BTW, note that this forum is for visual studio bugs, not yours. As said above, it's highly implausible that the compiler breaks such a basic statement. It's highly plausible that you made a mistake somewhere in your program that reproduces the observed behavior, or that you're improperly using the debugger.
Now, to exclude the possibility of a debugger viewer bug, place an "_ASSERT( a == &(cgm.o->m_metafileVersion) );" at the break point. If this gives a runtime error, ask a moderator to move the thread to the Visual C++ Programming forum; then, post the smallest but complete piece of code capable of reproducing the problem.
I tried and there is no runtime error.
as I told you,
doesn't work as it should be, that's why I try to find help here. I don't understand.Code:long *l = &(cgm.o->m_metafileVersion);
I've got a class with a pointer to an object from the lib I use to read CGM files :
I load it with that function :Code:class CGM
{
public:
CCgmObjects *o;
public :
CGM():o(NULL){}
~CGM(){if(o)delete o;}
int load(const char* pFilename);
};
but, again, it's not a programing problem. It's like if it is a Visual C++'s bug. The visual installation seems to be good...Code:int CGM::load(const char* pFilename){
CConfig *pConfig = new CConfig();
if (pConfig != 0)
{
// create a CgmObjects instance and Load the CGM file
o = new CCgmObjects(pConfig, NULL);
if (o != 0)
{
std::string userFontsDir = ".";
// Load the CGM file
error = o->LoadFile(pFilename);
if (error != 0)
{
printf("cannot open the file");
}
}
}
Maybe there is a param or something in the project configuration?
Quote:
Originally Posted by ArnaudCas
- How should it work and how does it work?
- Your code snippet does not contain the line you referred to.
- Did you try with ASSERT as superbonzo suggested?
Ok if I write :Quote:
How should it work and how does it work?
it should be :Code:long *l = &(cgm.o->m_metafileVersion);
a = 0x053e3d28
&(cgm.o->m_metafileVersion) = 0x053e3d28
but it is :
a = 0x053e3d50
&(cgm.o->m_metafileVersion) = 0x053e3d28
Yes you are right, sorry for that. The line is in the main, just after the call of the load method.Quote:
Your code snippet does not contain the line you referred to.
something like :
Code:int main(){
CGM cgm;
cgm.load("C:/myCGM.cgm");
long *a = &(cgm.o->m_metafileVersion);
_ASSERT( a == &(cgm.o->m_metafileVersion) );
}
Yes I did!Quote:
Did you try with ASSERT as superbonzo suggested?
And what?Quote:
Originally Posted by ArnaudCasYes I did!Quote:
Originally Posted by VictorN
Did you get the "Assertion failed!" message?
I have taken a look in my crystal ball and saw a parallel world in which somebody is trying to Debug in a Release build.
Pretty weird, isn't it? ;)