Date: Mon, 7 Sep 1998 20:21:56 -0400 (EDT) From: HighWind Software Information <info@highwind.com> To: freebsd-current@FreeBSD.ORG Cc: jb@cimlogic.com.au Subject: Re: Thread Problems Message-ID: <199809080021.UAA04192@highwind.com> In-Reply-To: <199809072254.RAA06607@ns.tar.com> (lists@tar.com)
next in thread | previous in thread | raw e-mail | index | archive | help
Seems to me that libc_r can call free() from within a signal handler. Given the non-recursive nature of this call, this is a serious problem: SIGVTALARM comes in (to check for context switching right?), _thread_sig_handler gets it, it can (and does) call _thread_kern_sched, _thread_kern_sched calls free() in a number of different places. This (to my libc_r-newbie-eyes) is *BAD*. Besides getting that message printed, can this cause corruption of data? Should I open a PR? -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?199809080021.UAA04192>