Date: Mon, 7 Sep 1998 22:47:53 -0700 (PDT) From: Archie Cobbs <archie@whistle.com> To: info@highwind.com (HighWind Software Information) Cc: freebsd-current@FreeBSD.ORG, jb@cimlogic.com.au Subject: Re: Thread Problems Message-ID: <199809080547.WAA05469@bubba.whistle.com> In-Reply-To: <199809080021.UAA04192@highwind.com> from HighWind Software Information at "Sep 7, 98 08:21:56 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
HighWind Software Information writes: > 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? Definitely.. the more specifics, the better, of course. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com 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?199809080547.WAA05469>