From owner-freebsd-current Mon Sep 7 14:32:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09981 for freebsd-current-outgoing; Mon, 7 Sep 1998 14:32:18 -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 OAA09976 for ; Mon, 7 Sep 1998 14:32:16 -0700 (PDT) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id RAA03755; Mon, 7 Sep 1998 17:15:04 -0400 (EDT) Date: Mon, 7 Sep 1998 17:15:04 -0400 (EDT) Message-Id: <199809072115.RAA03755@highwind.com> From: HighWind Software Information To: phk@critter.freebsd.dk CC: freebsd-current@FreeBSD.ORG In-reply-to: <26273.905200961@critter.freebsd.dk> (message from Poul-Henning Kamp on Mon, 07 Sep 1998 22:42:41 +0200) Subject: libc_r trouble and 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." bad. It means that you're trying to malloc in a signal handler (99.9% of the cases), which isn't really allowed... I agree. That is a bad thing to do. I just wish the program in question HAD a signal handler. The only "signal handling" going on would be inside libc_r.a. A quick grep of /usr/src/lib/libc_r/*/*.c CERTAINLY shows "malloc()" being called. However, I don't know much about when libc_r code runs. Does this sound like something that could happen? Now I'm getting very worried! -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message