Date: Sun, 17 Feb 2008 17:50:40 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Michiel Boland <michiel@boland.org> Cc: freebsd-current@freebsd.org Subject: Re: PRINTF_BUFR_SIZE (Re: 7.0 RC2 kernel panic with Kqemu/AMD64) Message-ID: <47B865E0.20407@FreeBSD.org> In-Reply-To: <Pine.GSO.4.64.0802171725190.9051@neerbosch.nijmegen.internl.net> References: <43555.82.234.78.29.1203154742.squirrel@secure.synsport.net> <20080216175811.GA33393@saturn.kn-bremen.de> <47B7352B.1040302@marino.st> <20080216210731.GA40417@saturn.kn-bremen.de> <55528.82.234.78.29.1203252678.squirrel@secure.synsport.net> <20080217160642.2ac9363e@peedub.jennejohn.org> <Pine.GSO.4.64.0802171725190.9051@neerbosch.nijmegen.internl.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michiel Boland wrote: > On Sun, 17 Feb 2008, Gary Jennejohn wrote: > > [...] >> I can't help with your problem, but I suggest that you add >> options PRINTF_BUFR_SIZE=128 >> to your kernel config file to avoid the above corrupted output. > > Any reason why this PRINTF_BUFR_SIZE option isn't in GENERIC on all > platforms? At the moment it is set for sun4v only. > > Cheers > Michiel > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > I think the fear is that it could cause a stack overflow because it allocates a character array (128-bytes in the above case) on the stack. I would like to know how real this fear is though. Clearly we do need a way to avoid interleaving console output by default. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47B865E0.20407>