Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Release & Debug
- Thread starter alehawk
- Start date
it may be because of the libraries you're linked to. if you linked to any libraries that have a 'd' as the last character of their name,(libcmtd.lib) that denotes a debug library and there will be an issue between mixing with debug and release libraries. I don't know if this is your problem, but I had that problem once before and that's what it was
bdiamond
bdiamond
This question comes up at this forum(s) again and again.
As usually exceptions in release mode are raised in consiquence of insidious errors not detected in debug mode.
As usually it is memory crash, memory leaks etc errors.
Don't be delused: debug mode as such is not 100% guarantee.
Common way to go: localize source of exception, select proper snippets and ask more help...
Apropos: you may get more exceptions in release mode with optimization. It's normally. The other compile mode is equal to the other machine code is equal the other program! Debugging is a process, not an event...
As usually exceptions in release mode are raised in consiquence of insidious errors not detected in debug mode.
As usually it is memory crash, memory leaks etc errors.
Don't be delused: debug mode as such is not 100% guarantee.
Common way to go: localize source of exception, select proper snippets and ask more help...
Apropos: you may get more exceptions in release mode with optimization. It's normally. The other compile mode is equal to the other machine code is equal the other program! Debugging is a process, not an event...
- Status
Similar threads
- Locked
- Question