Re: dbg_break macro

On 07/06/2024 04:55, David Brown wrote:

Certainly dbg_break is a better name, IMHO.  But I'd want a reason for the halt, especially if you are not running the code under a debugger at the time.

I have many samples of the usage of assert(0) being
"debug break, check this!, it can be an error"
if (condition1) {
   //...
}
else if (condition2) {
   //...
}
else if (condition3) {
   #warning TODO case 3 not implemented
   dbg_break("TODO case 3 not implemented");
}
if (ResourceNotAvailable())
{
    dbg_break("really unexpected");
    return -1;
}
etc