Date: Sat, 2 Nov 2002 14:59:04 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Conrad Sabatier <conrads@cox.net> Cc: current@freebsd.org Subject: Re: A few questions Message-ID: <20021102125904.GB2314@gray.sea.gr> In-Reply-To: <XFMail.20021102003920.conrads@cox.net> References: <20021101120227.GB1778@gray.sea.gr> <XFMail.20021102003920.conrads@cox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-11-02 00:39, Conrad Sabatier <conrads@cox.net> wrote: >On 01-Nov-2002 Giorgos Keramidas wrote: >> On 2002-10-31 18:39, Conrad Sabatier <conrads@cox.net> wrote: >>> And finally, is there a simple way to ensure that none of the debugging >>> code (including INVARIANTS stuff) is included during a buildworld? >> >> INVARIANTS and WITNESS are kernel-only stuff. They shouldn't affect >> your userland programs. If they do, it's probably a bug. > > I just happened to notice this: > > $ grep -r 'CFLAGS.*INVARIANTS' /usr/src > /usr/src/gnu/usr.bin/cc/Makefile.inc:#CFLAGS+= -DWANT_COMPILER_INVARIANTS > /usr/src/lib/libc_r/Makefile:CFLAGS+=-D_PTHREADS_INVARIANTS > /usr/src/lib/libpthread/Makefile:CFLAGS+=-D_PTHREADS_INVARIANTS Ah, good catch. It seems that _PTHREADS_INVARIANTS is enabled in libc_r and libpthread unconditionally. It's not related to the kernel INVARIANTS option, but looking at the under src/lib/libc_r I can see that it enables a few extra checks and panic()s here and there. Since I've been running "with" the checks for a while, and never paniced because of libc_r it's probably safe to remove. Giorgos. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021102125904.GB2314>