On Wed, Jun 25, 2008 at 04:15:58PM +0100, Darren J Moffat wrote: > Garrett D'Amore wrote: >> Can we have an environment variable to turn off this behavior for >> debugging purposes (perhaps leaving it turned off by default in a debug >> build of ON?) > > I don't think that is a good idea. None of the other platforms I viewed > have this and we didn't have this with SunOS 4.x either. More importantly > I don't like the idea of having to check an environment variable on every > printf(3C) family call, there could be a noticable performance hit for > that. >
i agree with garrett here. it would be nice to have an enviroment variable to disable this functionality. currently, libc has a handfull of different env variables that control debugging behavior. all these variables are checked once during libc init (see etest()) and then cached in tls for speed. i regularly use LIBTHREAD_ERROR_DETECTION to find and file bugs. if there was an environment variable to control this behavior i would enable it by default in my environment. ed
