From owner-freebsd-current Mon Sep 7 22:05:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01881 for freebsd-current-outgoing; Mon, 7 Sep 1998 22:05:26 -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 WAA01871 for ; Mon, 7 Sep 1998 22:05:16 -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 GAA27620; Tue, 8 Sep 1998 06:58:45 +0200 (CEST) To: HighWind Software Information cc: freebsd-current@FreeBSD.ORG Subject: Re: libc_r trouble and free() called recursively In-reply-to: Your message of "Mon, 07 Sep 1998 17:15:04 EDT." <199809072115.RAA03755@highwind.com> Date: Tue, 08 Sep 1998 06:58:44 +0200 Message-ID: <27618.905230724@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199809072115.RAA03755@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... > >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! run the program under a debugger, with setenv MALLOC_OPTIONS AJ and you should get a chance to see where it happens -- 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