[ros-dev] [ros-diffs] [sginsberg] 35600: - Remove KEBUGCHECK and KEBUGCHECKEX macros - Replace "KeBugCheck(0)" by ASSERT(FALSE) - Replace deprecated "CPRINT" by DRINT1
stefan__100__ at hotmail.com
Tue Aug 26 15:37:03 CEST 2008
Yes, I do know that ASSERT(FALSE) only occur in debug mode. However, I think this change is safe. Many of the KEBUGCHECK(0) usages are for unimplemented or very rare cases which shouldn't be hit, and the largest use of KEBUGCHECK(0) was in Mm (and the worst that could happen there is that ros survives a little longer).
Anyway, I will look into re-adding KeBugCheck with proper bugcodes where appropriate.
> Date: Sun, 24 Aug 2008 20:15:38 +0200
> From: hpoussin at reactos.org
> To: ros-dev at reactos.org
> Subject: Re: [ros-dev] [ros-diffs] [sginsberg] 35600: - Remove KEBUGCHECK and KEBUGCHECKEX macros - Replace "KeBugCheck(0)" by ASSERT(FALSE) - Replace deprecated "CPRINT" by DRINT1
> sginsberg at svn.reactos.org a écrit :
> > Author: sginsberg
> > Date: Sun Aug 24 10:48:05 2008
> > New Revision: 35600
> > URL: http://svn.reactos.org/svn/reactos?rev=35600&view=rev
> > Log:
> > - Remove KEBUGCHECK and KEBUGCHECKEX macros
> > - Replace "KeBugCheck(0)" by ASSERT(FALSE)
> > - Replace deprecated "CPRINT" by DRINT1
> You probably understand that KEBUGCHECK(0) is *NOT* the same as
> ASSERT(FALSE) is valid only in debug mode, and lets the code continue in
> release mode.
> KEBUGCHECK stops the execution also in release mode.
> For example, in ntoskrnl/dbgk/dbgkobj.c, code now continues even if
> DbgkpQueueMessage failed. Are you sure it is safe to continue in that case?
> (same question applies for other locations)
> Ros-dev mailing list
> Ros-dev at reactos.org
Discover the new Windows Vista
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ros-dev