Skip to main content
GameDev.net gamedev.net
🔒 Locked

Remote Debugging with DDraw

Started by Teric Jun 12, 2002 at 5:32 AM 3 replies 550+ views
Original Post
Teric
Teric
I have two machines at home, and I''m trying to use remote debugging under VC++6.0. I have no problems with it normally--I''ve been able to remote debug my programs in the past. However, whenever my program includes a DirectDraw surface, and I perform a DDrawSurface->Lock() function on it, the remote debugger drops out and won''t cooperate. When I start debugging, the 2nd monitor goes black for a second like it''s trying to set up the surface, then drops back out to Windows without even an error message. Has anyone seen this before? Is there a way around it? This is really frustrating, because now anytime I want to use a Lock() function on a DDraw surface, I can''t use remote debugging. (*sigh*) In order to debug at this point, I''ve had to drop out messages to a text file and debug after the fact. Thanks in advance!
I am always open to feedback, positive or negative...
Teric
Teric
*BUMP*

Anybody have an idea of how to get around this? Thanks!
I am always open to feedback, positive or negative...
Teric
Teric
*sigh*

Last bump... I hope someone might know how to resolve this problem.
I am always open to feedback, positive or negative...
Alimonster
Alimonster
This is a *complete stab in the dark*... try adding in the flag DDLOCK_NOSYSLOCK when you lock the surface.
Teric
Teric
OH MY GOSH!!! WOOOOHOOOO!!! IT WORKS!!

My wife says: that was a *very* well placed stab in the dark!

THANK YOU SO MUCH--THIS WILL MAKE LIFE SOOOO MUCH EASIER FOR ME!
I am always open to feedback, positive or negative...

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.