Please use /check with /debug or /full_debug

Folks, I encourage all of you to compile all your tasks with such combinations of compilation switches

/check /debug /check /full_debug /check /debug /undef

I still sometimes have crash either during compilation at run time or debugging with sdbg64 if I use /check.

If we all find small demo examples which crash then Silverfrost might faster find the reason.

Sending to Silverfrost my large code with instructions what's to do with it would be a PITA for me and Silverfrost. Also I'm still guessing if such crashes in my cases are due to very large requirements on memory 60GB or more or something because only ones somebody reported this (probably that was mecej4)

/check includes /debug. /undef includes /check.

/checkmate includes /undef.

So most users can use /checkmate but only for development and testing. There are high overheads.

There's a free plug for Silverfrost in my latest YouTube video.

https://www.youtube.com/watch?v=w9frx0vgwbw

Not the most exciting of topics, unless you are a sparky 😄

Paul, If /check includes /debug then is this an error when applying these two compilation switches

/check /debug

or it is just a redundant causing no harm?

John, In this post we tried kind of 'multiusers multitasking': the all users orchestrated massive bug hunt 😃

One thing I found is that users tend not to report the bugs, they always get workarounds instead and wait others will report. So how we can make any software to be as clean as possible for as short time as possible ? Will see if activating all may help

Dan

It is redundant causing no harm.