Project settings

[adonisv]

I'm using visual studio 6.0 and I've been tweaking the project settings on my project. However, now I can't run the debugger. Everytime I try to set a breakpoint I get a message saying the break point cannot be set and so it will be disabled and debugging will start at the beginning of the program. Any ideas? X| Under project settings, under the Link tab, I do have "Generate debug info" checked. I was previously getting an error saying this project contained no debug information. Now I can't set a break point. I must be missing something. A clue? Yes, that's it! :confused:

[Carlos Antollini]

Your current setting is in debug mode? May be you are in release mode... Try to recompile all the project.... Best Regards Carlos Antollini Do you know piFive[^] ?

[adonisv]

Debugging in Release Mode I've heard a myth repeated many times by my fellow VC++ developers. It is that it is not possible to debug in Release Mode. Fortunately, this is a myth. Rule 7: When all else fails try debugging in release mode. It is possible to debug in Release mode. The first step is to turn on symbols: * In Project Settings (Alt-F2) under the "C++/C tab" set the category to "General" and change the Debug Info setting to "Program Database". * Under the "Link tab" check the "Generate Debug Info" tab. * Recompile using "Rebuild All" This will allow you to see the symbols in the release version. You might want to also consider the following: * You may want disable your optimization settings when debugging your release version (though this isn't absolutely necessary). * If you have trouble placing breakpoints, the command "__asm {int 3}" will cause your program to stop at that line (be sure to remove these lines from your program when you are done debugging). That worked! :-D

[Prakash Nadar]

The difference between release mode and debug mode is the Debug info in your code and the type of libs liked, when you turn on those options, you have effectivly turned the Release mode build to debug mode build

---

Tech.Support : Mam, is your pc running under windows? Customer : No actually its close to the main door.

[Steve S]

But you can have a release build which is optimised, links to the non-debug versions of various libs/dlls and still contains debug info. Of course, the info is of more limited use, since the compiler may well have reordered parts of the object code. Steve S

[Mike Dimmick]

John Robbins (of MSDN Magazine's Bugslayer column) recommends always compiling your release builds with debugging information turned on. You just don't distribute your debugging symbols to the end customer. Enabling the /DEBUG switch to the linker causes it to go a little pessimistic and include everything from all libraries. For a release build, you'll probably want to turn /OPT:REF on, which tells it to only include referenced blocks. In combination with the /Gy compiler switch, this causes any unreferenced code and data to be eliminated, reducing the size of your executable. If your program crashes, you can now use tools like CrashFinder[^] (look about half-way down the page) to turn the crash address into a source file and line number.

[adonisv]

I'm trying to switch my project back to Debug mode, but it won't run under those settings. I've got the project settings to Win32 Debug and I've got the project configurations set to Win32 Debug. What else do I need? :confused:

[Steve S]

That should be enough. When you say it won't run, what does that mean, exactly? Won't compile, won't execute under debugger, or what? Steve S

[adonisv]

I get a debug assertion failed error message. :sigh: The debugger then points to this section of the "windows" code when I try to debug the problem... void CWnd::MoveWindow(int x, int y, int nWidth, int nHeight, BOOL bRepaint) { ASSERT(::IsWindow(m_hWnd)); if (m_pCtrlSite == NULL) ::MoveWindow(m_hWnd, x, y, nWidth, nHeight, bRepaint); else m_pCtrlSite->MoveWindow(x, y, nWidth, nHeight, bRepaint); } :((