Re: Mac OS X 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
Re: Mac OS X 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
- Subject: Re: Mac OS X 10.4 (Tiger) compilation errors ( GCC v3.3 ) with X Code 2.0 tool
- From: Andrew Gallatin <email@hidden>
- Date: Tue, 9 Aug 2005 09:47:53 -0400 (EDT)
Karunakar Reddy G writes:
> Hi,
> Thanx for previous help,
> I do know how to handle user address to use on copyin/copyout functions.
> I did in this way, it works fine, may be dirty type casting (some what
> double pointer type)
> user_addr_t user_buffer = (user_addr_t) foo;
> where "foo" is void * I/O input structure (32 bit pointer) passed as a
> argument from user application
How are you communicating with the user-space application? BSD
ioctls, or something from IOLib?
You must ensure that you're not talking to a 64-bit process, or else you
risk copying to/from the wrong address. Since you're using
copy{in/out}, that means you're talking to the current process,
and you can easily check this with the proc_is64bit() kpi.
Drew
_______________________________________________
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