From owner-freebsd-amd64@FreeBSD.ORG Tue Oct 26 13:42:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22B8416A4CE for ; Tue, 26 Oct 2004 13:42:13 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 714EE43D3F for ; Tue, 26 Oct 2004 13:42:12 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i9QDgA9S029045; Tue, 26 Oct 2004 15:42:11 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <417E5432.1070004@withagen.nl> Date: Tue, 26 Oct 2004 15:42:10 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Pentchev References: <20041026115041.GE2841@sivokote.iziade.m$> <417E474A.1000401@withagen.nl> <20041026125709.GF1003@straylight.m.ringlet.net> <417E4D6C.4040508@withagen.nl> <20041026133002.GG1003@straylight.m.ringlet.net> In-Reply-To: <20041026133002.GG1003@straylight.m.ringlet.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Georgi Guninski cc: freebsd-amd64@freebsd.org Subject: Re: two 4GB mallocs => SEGV X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 13:42:13 -0000 Peter Pentchev wrote: [snip] >>>>>on a freebsd amd64 box with more than 8GB swap i experience the >>>>>following: This is of course where strange things start. This should not be possible when al things are as suggested. 2*4G allocs should work. [more snip] >>>>what does swapinfo tell you during the the run of the program??? So what that tell you... BTW. I ran the program with 3*2Gb alloc (I got 4GB and 5Gb swap) malloc.conf -> XZ => Give text warnings, and zero everything But still I get: [/tmp] root@opteron> ./a.out 80000000 503000 80503000 100503000 And no further text. So this is consistent with previous findings that the text gets lost somewhere... But it does not dump core??? where X would tell it to do so. > I looked at the source before posting that - src/lib/libc/stdlib/malloc.c, > and the handling of malloc_xmalloc invokes wrterror(), which writes to > stderr before aborting. Oke, should be correct then? >>I think that std-malloc settings were AX for anything before -STABLE. > Actually they were 'AJ', not 'AX', and they were turned off on Sep 7 for > RELENG_5. Georgi's uname shows 5.3-BETA6, which was cut about Sep 23, > so neither 'J' nor 'X' ought to be set by default. could very well be so. > Still, Georgi, can you check if you have a MALLOC_OPTIONS variable or > a /etc/malloc.conf symlink? I've found that settings not always worked the way I fully expected them. Still got a test for 0xdeaddead in a program which explicitly sets Z in its malloc-settings --WjW