Disable ASSERTS

[misha_grewal]

How to disable all the ASSERTS that come when u execute a program in Debug mode?I require it very urgently. The ASSERT i m getting are in timecore.cpp and i have no idea how to remove them. But they are occurring so frequently that its difficult to operate on the debug mode application. Any comiler setting or macro which would disable all ASSERTs from popping up? Any ideas about ASSERTS in timecore.cpp?

[Christian Graus]

The ASSERTs are telling you something, you should listen to them. You could try redefining ASSERT, and see if that works out for you. Or undefine DEBUG, but then you may as well go to release mode. Christian I have drunk the cool-aid and found it wan and bitter. - Chris Maunder

[rpins]

Most ASSERT macros (I'm assuming you're using some Microsoft version of them) are enabled in debug compilations and then nullified for release versions. In other words, an ASSERT macro might be defined like this: #ifdef _DEBUG #define ASSERT(expr) ...some assert code... #else #define ASSERT(expr) #endif Notice how the second ASSERT defition has nothing after it. That's because in non-debug builds, you don't want assertions to do anything. So, to possibly answer your question, you should probably dig up where your ASSERT is being defined and do #undef _DEBUG (to undefine debug build). Unfortunately, that turns off most debug features since many things test against _DEBUG being defined. Either do that, or compile as release, or create your own ASSERT macro based on other example code. HTH

[l a u r e n]

ummmmm how about fixing the cause of the ASSERT's? just a wild stupid idea i know but im old fashioned like that :rolleyes:

---

"there is no spoon"
biz stuff   about me

[Prakash Nadar]

I already told him to do that in the previous post but he says he has no time to do that(that was 3-4 days back), if he had taken some time off to fix the problem then his prob would have been solved. I Touched Osama Bin Ladens Bushy Beard

[Rob Manderson]

Christian Graus wrote: The ASSERTs are telling you something, you should listen to them Uh huh :) Some of my friends complain when I sprinkle my code liberally with ASSERT and ASSERT_KINDOF but I almost never have problems with NULL pointers or pointers to objects of the wrong kind. Even the act of writing the assertion gets the background threads thinking about whether I'm calling something with the correct (and validated) pointers :) Rob Manderson http://www.mindprobes.net **Paul Watson wrote:**What sense would you most dislike loosing? Ian Darling replied. Telepathy Then I'd no longer be able to find out everyones dirty little secrets The Lounge, December 4 2003

[misha_grewal]

Thnks, I finally fixed the ASSERT. :)