Strange Instruction Pointers
Strange Instruction Pointers
- Subject: Strange Instruction Pointers
- From: Ricky Sharp <email@hidden>
- Date: Wed, 9 Jun 2004 16:57:55 -0500
I have a native carbon app project in Xcode 1.2 running on 10.3.4.
Recently, when stepping into the constructors of my objects, the
debugger displays this for thread-1 just after I step into a line such
as CObject* anObject = new CObject()
# Thread-1
0 operator new(unsigned long)
1 main
The highlight is on the operator new line and the debugger brings up a
completely unreleated file and places the current instruction pointer
on that line.
For example, it just stopped on the following line:
CFStringRef IIShellStrings_PreferencesFileName = CFSTR ("Preferences
File Name");
In other situations, stepping into constructors will stop on inline
functions of some unrelated object.
If I step out, then back in, my stack trace them becomes:
# Thread-1
0 CObject::CObject
1 main
I tried duplicating this issue with the stock Carbon app template. I
then modified it to declare this class:
class CObject
{
private:
int mX;
public:
CObject (int x) { mX = x; }
};
and in main, I did:
CObject* anObject = new CObject (0);
Stepping in on that line in main jumps to the correct constructor line.
Back to the problematic app...it's a debug build and all optimizations
are turned off. I also have ZeroLink disabled. Is this a bug in the
debugger? Or is this a sign of some sort of memory corruption in my
app? The app has been running beautifully though; no crashes or
signals raised.
___________________________________________________________
Ricky A. Sharp mailto:email@hidden
Instant Interactive(tm) http://www.instantinteractive.com
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.