Date: Thu, 22 Aug 2002 13:57:22 +0200 (CEST) From: Martin Blapp <mb@imp.ch> To: Don Lewis <dl-freebsd@catspoiler.org> Cc: <tlambert2@mindspring.com>, <sos@freebsd.dk>, <marks@ripe.net>, <ktsin@acm.org>, <freebsd-current@FreeBSD.ORG> Subject: Re: Memory corruption in CURRENT Message-ID: <20020822135515.Y45839-100000@levais.imp.ch> In-Reply-To: <200208221023.g7MANUwr036757@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, as far as I can tell it is really reather easy to hide the bug. All these options did hide the bug for some time: - Use -g to compile the segfaulting binarys - Remove -g to compile the segfaulting binarys - Use a kernel compiler on another machine - New hardware They just disappeared after such an action, but showed up again later after some buildworlds. Martin Martin Blapp, <mb@imp.ch> <mbr@FreeBSD.org> ------------------------------------------------------------------ ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP: <finger -l mbr@freebsd.org> PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E ------------------------------------------------------------------ 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?20020822135515.Y45839-100000>