🔒 Locked

Debugging Direct X

Started by Viri- Oct 26, 2000 at 1:44 PM 1 replies 200+ views

Original Post

Oct 26, 2000 at 1:44 PM

Debugging Direct X Ok I''m working on a P-III 500mhz 128 mb ram. TNT video card, 25gb HD and that sort. I also have to laptops, a P-166mhz and a P-90mhz that are networked with a home networking kit. All but the P-90 has Windows 98 on it. (it has Linux) And last I have a dx2-66mhz computer. It''s in parts. But I have another monitor with it as well as a video card also. My options as I see it is to set up another monitor or setup remote debugging. I was wondering what would be best and also if anyone would give me any info on setting both of those two options up. (especially anything I need to know about setting up my other monitor because that, at least for now seems to be a better, faster option.) Also right now if I try to debug my programs it won''t allow me to set breakpoints.. If I try it says that they aren''t valid and will be unset and the program will stop at the beginning of the program. Of course that''s not what I need. Any idea of what I need? Also if anyone would be willing to throw in a few tips on debugging please do. Thanks, Viri-

mr_jrt

Oct 26, 2000 at 4:44 PM

Check you''re not compiling in release mode. Release mode obviously has no debugging information in the exe, so you can''t set breakpoints. If you do try to debug it, the debugger will stop at the entry point (WinMain) after which you cannot really break into the code safely.

As for remote debugging, it''s a pice of p**s to set up. In the documentation it will tell you what files you need to get from your VC++ directory, and you then copy these to the remote machine.

Next, run the remote debug monitor on the remote pc. When you''ve done that, go into the build menu and select "Debugger remote connection". Choose TCP/IP and stick the IP of the remote machine in the settings dialog.

Finally, check the project settings debugging paths are network paths so the remote pc can find the files,
e.g. \\host\c++\project\debug\test.exe
and not c:\C++\debug\test.exe

And thats it.

When you run the program (debug or not) it will run on the remote machine instead.

(ps, tell it not to look for dll''s when it asks)

I''ve found it real useful several times, and a lot easier than multi-monitor.

Waassaap!!

Topic Locked

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