From owner-freebsd-current Mon Sep 7 13:47:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02419 for freebsd-current-outgoing; Mon, 7 Sep 1998 13:47:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02409 for ; Mon, 7 Sep 1998 13:47:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id WAA26275; Mon, 7 Sep 1998 22:42:42 +0200 (CEST) To: HighWind Software Information cc: freebsd-current@FreeBSD.ORG Subject: Re: free() called recursively In-reply-to: Your message of "Mon, 07 Sep 1998 16:29:18 EDT." <199809072029.QAA03642@highwind.com> Date: Mon, 07 Sep 1998 22:42:41 +0200 Message-ID: <26273.905200961@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199809072029.QAA03642@highwind.com>, HighWind Software Information writes: > >How bad is it to get this: > "t_activefile in free(): warning: recursive call." bad. It means that you're trying to malloc in a signal handler (99.9% of the cases), which isn't really allowed... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message