Date: Mon, 7 Sep 1998 17:15:04 -0400 (EDT) From: HighWind Software Information <info@highwind.com> To: phk@critter.freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: libc_r trouble and free() called recursively Message-ID: <199809072115.RAA03755@highwind.com> In-Reply-To: <26273.905200961@critter.freebsd.dk> (message from Poul-Henning Kamp on Mon, 07 Sep 1998 22:42:41 %2B0200)
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809072115.RAA03755>