Messages in this thread | | | Date | Sat, 31 Jul 1999 12:47:25 +0200 | From | Lars Marowsky-Bree <> | Subject | Re: Useful KERNEL_ASSERT Macro |
| |
On 1999-07-31T01:59:40, Kent Overstreet <kento@pobox.alaska.net> said:
> What about implementing this specific to the function? i.e. you usually > wouldn't turn on all the asserts, just the ones for the function you > thought had the bug.
Maximum debug mode is an exceptionally good idea. "Writing Solid Code" calls this "Fortify your subsystems" and I wholeheartedly agree.
The ones who you thought had the bug are most likely to be the ones who are perfectly fine, if we pay any attention to Murphy ;-)
If this is done in a kernel macro or not is beyond my understanding of the kernel code, though it appears to make sense to me. However, it is a good idea to add as many of these assertions as possible.
(That having many assertions will make the kernel timing change and most heisenbugs will disappear when you start debugging is another problem)
Sincerely, Lars Marowsky-Brée
-- Lars Marowsky-Brée Network Management
teuto.net Netzdienste GmbH - DPN Verbund-Partner
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |