From owner-freebsd-bugs Wed Sep 6 3:10: 8 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B5D6837B424 for ; Wed, 6 Sep 2000 03:10:06 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id DAA82813; Wed, 6 Sep 2000 03:10:06 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 6 Sep 2000 03:10:06 -0700 (PDT) Message-Id: <200009061010.DAA82813@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/21075: top: can't allocate sufficient memory Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/21075; it has been noted by GNATS. From: Sheldon Hearn To: lan@kru.ru Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/21075: top: can't allocate sufficient memory Date: Wed, 06 Sep 2000 12:05:02 +0200 On Wed, 06 Sep 2000 00:50:48 MST, lan@kru.ru wrote: > >Number: 21075 > >Category: bin > >Synopsis: top: can't allocate sufficient memory This happens because top needs 7 lines for headers. display_resize() calculates that the number of lines available is -1 and returns this value. As it happens, display_init() interprets this -1 return value as a memory allocation error. I'm downloading top-3.5beta9 to see whether this problem is fixed in that version. As a work-around, you can use top's -b (batch mode) option. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message