This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: timetable change on mingw-libgcj
- From: Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'Adam Megacz'" <gcj at lists dot megacz dot com>, java at gcc dot gnu dot org
- Date: Tue, 18 Dec 2001 15:09:00 +1300
- Subject: Re: timetable change on mingw-libgcj
- References: <40700B4C02ABD5119F000090278766443BEE47@hplex1.hpl.hp.com>
Boehm, Hans wrote:
>How are MacOSX threads implemented? Do they map directly to kernel threads?
>
Yes, theres an overview of the Mac OS X threading here:
http://developer.apple.com/techpubs/macosx/Essentials/SystemOverview/InverEnvironissues/Threading_Packages.html
The only problem with that nice diagram is that the posix threads
support isn't actually complete.
>
>Is there a way to stop a thread other than by sending it a signal?
>
Mach does provide a thread_suspend() and thread_resume(), and you can
more or less mix direct mach calls with pthreads calls since pthreads is
just a layer over mach. I presume there is also a way to get the
register state of a suspended thread, but I havn't really looked yet.
Apple are planning to implement the missing pthreads functionality (ie
pthread_kill) at some point, but I wouldn't hold my breath ;-)
regards
Bryce.