Re: Obtaining non-exported symbol from kernel on runtime (without the debug symbols)
Re: Obtaining non-exported symbol from kernel on runtime (without the debug symbols)
- Subject: Re: Obtaining non-exported symbol from kernel on runtime (without the debug symbols)
- From: Michael Smith <email@hidden>
- Date: Sun, 14 Dec 2008 20:32:12 -0800
On Dec 14, 2008, at 7:47 PM, John D. wrote:
Yes. On purpose. I personally made the syscall table a private
symbol.
The problem is that it's a hassle for legitimate developers.
No, the "problem" here is that it's inconvenient for *you*.
You need to realise that "legitimate developers" have a broad variety
of concerns, many of which you have either discounted elsewhere in
this thread, or which possibly haven't occurred to you yet.
One of those legitimate concerns is the availability of stable,
supported interfaces. Those stable, supported interfaces are, in the
Darwin world, referred to as KPI.
They are what you get to play with. If what you want to do can't be
done via KPI, you have two options:
- Explain what it is you're doing, and why you want KPI to support
the activity. In time, if an interface can be created that will be
supportable and sustainable, then your request may result in changes
to KPI.
- Build your own kernel from publically available sources, and use
that.
Incidentally, users like stable, supported interfaces as well. The
sort of monkey business you're talking about tends to fail
spectacularly, and they don't like that. Typically when something
stupid breaks. users come running and complaining to Apple, despite
the fact that it's a third party that's wilfully ignored both
established guidelines and basic common sense.
= Mike
_______________________________________________
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