From owner-freebsd-current Sat Jul 15 2:36:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 3CA6437C20B for ; Sat, 15 Jul 2000 02:36:39 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-195-14-254-213.netcologne.de [195.14.254.213]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id LAA05890; Sat, 15 Jul 2000 11:36:36 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e6F9aUh02388; Sat, 15 Jul 2000 11:36:30 +0200 (CEST) Date: Sat, 15 Jul 2000 11:36:30 +0200 (CEST) From: Paul Herman To: Pascal Hofstee Cc: freebsd-current@FreeBSD.ORG Subject: Re: weird application coredumps .... In-Reply-To: <20000715112826.A13861@shadowmere.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jul 2000, Pascal Hofstee wrote: > Since a recent update of my CURRENT system i get weird coredumps from at > least two applications which just worked fine previously. The two programs > are tintin++ (mud-client) ... and licq (when trying to set myself to > "away-mode"). Just a wild guess, but this could be because of the recently added /etc/malloc.conf options -- (which are just for debuging purposes for now...) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message