Re: The status of NOTE_TRACK bug in kqueue
Re: The status of NOTE_TRACK bug in kqueue
- Subject: Re: The status of NOTE_TRACK bug in kqueue
- From: Quinn <email@hidden>
- Date: Mon, 25 Sep 2006 09:33:39 +0100
At 14:45 +0300 23/9/06, Nikita Zhuk wrote:
[...] monitoring the NOTE_TRACK event causes kernel panic as soon as
the parent process fork()s any children. This bug with a simple test
case has been posted to this list [1] in 2005, and based on the list
archives it has been also reported via bugreporter. Does anyone have
any updates on this issue? The bug is still present in Mac OS X
10.4.7, Darwin 8.7.1.
Just to be 100% clear, if a bug is affecting you, file it in BugReporter.
<http://developer.apple.com/bugreporter/>
Even if you think that it's been previously filed, file it again.
Closing duplicates is easy (and the number of duplicates against a
bug is, unofficially and to a limited extent, factored into its
priority), but fixing bugs we don't know about is hard.
This is especially true if you haven't seen a bug number for the bug.
If you have a bug number, it's trivial for Apple folks to look up the
status of the bug. If you don't have a bug number, it's hard for us
to look up the bug and there may not /actually/ be a bug.
* * *
Notwithstanding the above, I dug through Radar and I think the bug
that you're concerned about is being tracked as
<rdar://problem/3439519>. AFAICT, no progress has been made on it.
Sorry for the bad news.
S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden