I am using Microsoft Visual C++ (no microsoft barbs please, its the one we need for my course), and am having real problems with the debugger.
I couldn't get the debugger working so I burnt my program and took it to school and the teacher taught me how to use the debugger (it worked fine), but now that I am at home the debugger will work for about 2-3 lines before going into this ->
02F7251E jmp 02F7256B
02F72520 mov eax,1
From here I have no idea what is happening and can do nothing short of stopping the debugger, please note that it didn't do this on any other computer (tried 2 teachers computers).
It's hard to say without knowing what your debugging, but you will only be able to step into the functions where you have the source available. Some of the C runtime source provided in MSVC (in your CRT directory) is implemented in asm (functions like strlen()- in CRT\SRC\INTEL), so if you may be stepping into these functions. Or you might be looking at the disassembly of your exe.
But it is de-bugging perfectly on other computers, no problems at all no matter how far into the program we go. Yet on my computer it only goes 2-3 lines before going into dis-assembly window and the program wont start.
Make sure you compile your program for debug mode on your PC.
Yeah I got that part right in the configurations menus. There must be some other minor option I have missd though.
I keep getting the same 'error' messages when I start in debugger mode->
Loaded 'D:\WINNT\System32\ntdll.dll', no matching symbolic information found.
Loaded 'D:\WINNT\system32\OPENGL32.DLL', no matching symbolic information found.
Loaded 'D:\WINNT\system32\msvcrt.dll', no matching symbolic information found.
Loaded 'D:\WINNT\system32\KERNEL32.DLL', no matching symbolic information found.
I have all the .dll's but how do I find this symbolic info?
> I have all the .dll's but how do I find this symbolic info?
You should have either corresponding .sym files, or debug versions of the .dll files.
These should have been installed when you installed the compiler.
You should still be able to debug your code, but you'll have more difficulty when the code enters one of those .dll files. You'll be able to debug 'raw' as it were, and this is much harder than if you had the symbols loaded.
I have just re-installed visual C++ for the 6th time in 3 days, both my copy and a friends copy, with and without service pack 4 but the debugger simply will not work on my computer (windows 2000, pentium 3). I burnt my code again and went to a friends house to see if it works on another computer and it de-bugged fine.
Please help cause I am losing my sanity over this. It is in de-bug mode.