From owner-freebsd-current Mon Sep 7 13:29:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00189 for freebsd-current-outgoing; Mon, 7 Sep 1998 13:29:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00181 for ; Mon, 7 Sep 1998 13:29:22 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id QAA03642; Mon, 7 Sep 1998 16:29:18 -0400 (EDT) Date: Mon, 7 Sep 1998 16:29:18 -0400 (EDT) Message-Id: <199809072029.QAA03642@highwind.com> From: HighWind Software Information To: freebsd-current@FreeBSD.ORG Subject: free() called recursively Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How bad is it to get this: "t_activefile in free(): warning: recursive call." We are using gcc for C++. One of our test programs which tests code that currently sends our application out into "la-la land" seems to print this every few runs. During those runs, it also goes off into "la-la land". "la-la land" == running but going nowhere. ktrace shows nothing, application only dies with "kill -9". We do link against libc_r. I'm wondering if this recursive call thing is a serious problem and what we can do about it. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message