From owner-freebsd-hackers Sun Jan 18 08:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20145 for hackers-outgoing; Sun, 18 Jan 1998 08:21:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20113 for ; Sun, 18 Jan 1998 08:21:00 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA25235; Sun, 18 Jan 1998 08:24:25 -0800 (PST) Message-Id: <199801181624.IAA25235@implode.root.com> To: Chris Toshok cc: freebsd-hackers@FreeBSD.ORG Subject: Re: user limits, login.conf, etc. In-reply-to: Your message of "Sat, 17 Jan 1998 18:35:38 PST." <34C16A7A.9E950A3@netscape.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 18 Jan 1998 08:24:25 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk >I've been using freebsd for my work (on the navigator) for some time, >and am having a problem with 2.2.5. > >I've upped every conceivable limit that I run across, and I still get > >gdb: virtual memory exhausted: can't allocate 4072 bytes. > >when I try to debug netscape. The gdb process never gets above 32 megs, >and the netscape executable doesn't grow to more than 16 megs. > >The machine has way more than enough to handle this -- 128 megs >physical, and 400 megs of swap. > >Here's my login.conf entry: > >default:\ > :cputime=infinity:\ > :datasize=256M:\ > :stacksize=256M:\ > :memorylocked=256M:\ > :memoryuse=256M:\ > :filesize=infinity:\ > :coredumpsize=infinity:\ > :maxproc=infinity:\ > :openfiles=infinity:\ > :priority=0:\ > :requirehome@:\ > :umask=022:\ > :tc=auth-defaults: > >The kernel was compiled with: > >options "MAXDSIZ=(512*1024*1024)" >options "DFLDSIZ=(512*1024*1024)" > >Anyone have a clue? It's getting extremely frustrating debugging with >printfs. What does the shell report that about the limits? Which shell are you using? It sounds like there is another login.conf entry that is matching your login. Have you tried manually setting the limits to infinity prior to starting gdb? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project