what would cause the address saved in a pointer been changed when I am not doing any operation on that pointer?
consider the following situation:
I have 2 pointers, let's say a and b.
a points to a address which is acquired by malloc, let's say 0x100ef
and now, when I am doing some operation on pointer b, the address that is pointed
by a is suddenly changed, let's say a is pointing to 0x0033 now.
Is there any special details that I should take care when using pointer which I missed?
I could think of a few things I suppose (scope issues, fiddling with b when b points to a), but it would be easier to tell if you could cough up some details, ideally the actual code.
Assuming there isn't a compiler bug involved (compiler bugs happen in approximately 1 in a million of these cases), the reason that a pointer is modified when another pointer is changed is because the second pointer holds the address of the first pointer - either on purpose or by accident.Originally Posted by ptmstart
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
Buffer overruns are a good example: http://cpwiki.sf.net/Buffer_overrun
It you want to get to the bottom of it, it can take some good debugging. Fortunately, Visual Studio can help you catch these bugs very, very easily.
