Date: Tue, 08 Sep 1998 06:58:44 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: HighWind Software Information <info@highwind.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: libc_r trouble and free() called recursively Message-ID: <27618.905230724@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 07 Sep 1998 17:15:04 EDT." <199809072115.RAA03755@highwind.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27618.905230724>