From owner-freebsd-current Thu Aug 2 12:48:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id CA60E37B401; Thu, 2 Aug 2001 12:48:23 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id FAA06347; Fri, 3 Aug 2001 05:48:21 +1000 Date: Fri, 3 Aug 2001 05:45:47 +1000 (EST) From: Bruce Evans X-X-Sender: To: Maxim Sobolev Cc: , Subject: Re: rpc.umtall dumps core on each startup/shutdown In-Reply-To: <200108021748.f72HmW846514@vega.vega.com> Message-ID: <20010803054358.K2809-100000@besplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Maxim Sobolev wrote: > I found that the rpc.umntall program from time to time starts dumping a core > at each startup/shutdown. Removal of /var/db/mountab helps for certain > period of time, but eventually the problem reoccurs. Attached please find > backtrace of two cores (sig11 on shutdown and sig6 on startup) and > mountab from the affected machine. Please fix. > > I am observing this problem on two 5-CURRENT machines updated today. I haven't seen this, but I consistently see "chunk already free" messages. The differences is probably just due to my use of /etc/malloc.conf -> aj. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message