From owner-freebsd-current  Mon Sep  7 17:22:49 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA05706
          for freebsd-current-outgoing; Mon, 7 Sep 1998 17:22:49 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from highwind.com (hurricane.highwind.com [209.61.45.50])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05701
          for <freebsd-current@freebsd.org>; Mon, 7 Sep 1998 17:22:44 -0700 (PDT)
          (envelope-from info@highwind.com)
Received: (from info@localhost)
	by highwind.com (8.8.6/8.8.6) id UAA04192;
	Mon, 7 Sep 1998 20:21:56 -0400 (EDT)
Date: Mon, 7 Sep 1998 20:21:56 -0400 (EDT)
Message-Id: <199809080021.UAA04192@highwind.com>
From: HighWind Software Information <info@highwind.com>
To: freebsd-current@FreeBSD.ORG
CC: jb@cimlogic.com.au
In-reply-to: <199809072254.RAA06607@ns.tar.com> (lists@tar.com)
Subject: Re: Thread Problems
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


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