Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

Dark GDK / Variable watch problem

Author
Message
Lord of the Games
18
Years of Service
User Offline
Joined: 27th May 2005
Location: Netherlands
Posted: 10th Feb 2006 16:32
Link
I have a really weird problem with variable watch. The values in it change to really weird not assigned value's. char array's of private assign variables sometimes become bad pointers, or suddenly contain junk instead of the previous line assigned text. But the weiredest thing is the do have the correct data when printed to screen or file.
It makes my debugging realy hard because I never know the real data in my vars. Anyone know what might cause it?

DarkGameSDK
trying to understand DX...
Back to top
Profile PM Email
Barnski
18
Years of Service
User Offline
Joined: 26th Jan 2006
Location: Switzerland, Zurich
Posted: 10th Feb 2006 19:06 Edited at: 10th Feb 2006 19:11
Link
Are you sure ur compiling in debug mode?
If not, the release mode has probably the optimized flag set to 2 (or 3), which means I think optimize speed (or size) of executable.

Which further means that some instructions are changed in the order they are executed in assembly language. and therefore debuging doesn't work anymore synchronous with your source code.

-- I just started with DarkSDK, by translating DBP Projects. --
Back to top
Profile PM Email Website
Lord of the Games
18
Years of Service
User Offline
Joined: 27th May 2005
Location: Netherlands
Posted: 11th Feb 2006 18:28
Link
Thanks alot. It was indeed the problem. I was ready to rip my hair out, I never thought of it, because I put it in release to avoid the defaultlib LIBC conflicts. But thanks a whole bunch for fixing this for me.

DarkGameSDK
trying to understand DX...
Back to top
Profile PM Email
Barnski
18
Years of Service
User Offline
Joined: 26th Jan 2006
Location: Switzerland, Zurich
Posted: 11th Feb 2006 20:08
Link
To get rid of the defaultlib conflict you can do the following:

go to Project->Properties

Linker->Command Line

in the text field of "additional options" insert this:


This should get rid of the warning message.

greets,
Barnski

-- I just started with DarkSDK, by translating DBP Projects. --
Back to top
Profile PM Email Website
Lord of the Games
18
Years of Service
User Offline
Joined: 27th May 2005
Location: Netherlands
Posted: 12th Feb 2006 18:06
Link
Thanks, you fixed all my probs!

DarkGameSDK
trying to understand DX...
Back to top
Profile PM Email
Barnski
18
Years of Service
User Offline
Joined: 26th Jan 2006
Location: Switzerland, Zurich
Posted: 12th Feb 2006 23:53
Link
Your welcome

-- I just started with DarkSDK, by translating DBP Projects. --
Back to top
Profile PM Email Website
Back to top

Login to post a reply

Server time is: 2024-05-06 05:17:37
Your offset time is: 2024-05-06 05:17:37