while (TRUE); (when something is unimplemented) ---> ASSERT(FALSE); // while (TRUE...
authorHermès Bélusca-Maïto <hermes.belusca-maito@reactos.org>
Fri, 4 Jan 2013 12:31:46 +0000 (12:31 +0000)
committerHermès Bélusca-Maïto <hermes.belusca-maito@reactos.org>
Fri, 4 Jan 2013 12:31:46 +0000 (12:31 +0000)
commit4c4fd151f2812d148dc4f439d9617cfe82d46753
tree0859f99ce05a7925f03d383864cea139a20bbe5f
parentb70845423e53b3bceda10fc4dd43de606d21df19
while (TRUE); (when something is unimplemented) ---> ASSERT(FALSE); // while (TRUE); (unless we deal with a 'noreturn' function),
and in some cases, return an adequate value. In some places however, I add an ASSERT(FALSE); before keeping the while (TRUE); in critical regions.

(Only x86, as well as in r58110). More ASSERTS (in debug mode) or BSODs may appear, instead of having hung threads.

Part 1-bis/2

svn path=/trunk/; revision=58111
15 files changed:
reactos/lib/cmlib/hivecell.c
reactos/ntoskrnl/cache/cachesub.c
reactos/ntoskrnl/cache/copysup.c
reactos/ntoskrnl/cache/fssup.c
reactos/ntoskrnl/cache/logsup.c
reactos/ntoskrnl/include/internal/i386/ke.h
reactos/ntoskrnl/io/iomgr/irp.c
reactos/ntoskrnl/io/pnpmgr/pnpmgr.c
reactos/ntoskrnl/kd64/amd64/kdx64.c
reactos/ntoskrnl/kd64/arm/kdarm.c
reactos/ntoskrnl/ke/bug.c
reactos/ntoskrnl/ke/dpc.c
reactos/ntoskrnl/ke/i386/context.c
reactos/ntoskrnl/ke/i386/traphdlr.c
reactos/ntoskrnl/po/povolume.c