From owner-freebsd-current Thu Oct 17 11:05:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA17440 for current-outgoing; Thu, 17 Oct 1996 11:05:28 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA17430 for ; Thu, 17 Oct 1996 11:05:24 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA19142; Thu, 17 Oct 1996 12:05:15 -0600 (MDT) Date: Thu, 17 Oct 1996 12:05:15 -0600 (MDT) Message-Id: <199610171805.MAA19142@rocky.mt.sri.com> From: Nate Williams To: Keith Mitchell Cc: nate@mt.sri.com (Nate Williams), current@freebsd.org Subject: Re: Weirdness in current In-Reply-To: <199610171803.OAA23823@unix.guru.org> References: <199610171632.KAA18263@rocky.mt.sri.com> <199610171803.OAA23823@unix.guru.org> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Where is it dumping core? > > I checked my program again and did find a small bug in it that would cause > it to reference an array out of bounds. Its amazing that compiling in the > math library would fix this and the dynamic/static executable made a > difference. ;-) And at that only on output redirection. Go Figure. ;->> Stack corruption bugs are a *bugger* to find. The program has a completely different 'memory' allocation setup when used static vs. shared libraries due to mmap() usage in the shlib loader. In any case, we're glad everything's working now. :) Nate