Re: question on thread safe GLibc with Zaurus
David Hedbor <[email protected]> 22 Jan 2003 21:05:04 -0800
| Newsgroups | gmane.comp.handhelds.zaurus.devel |
|---|---|
| Organization | Eon Games |
| Message-ID | <[email protected]> |
Kyle Hayes <[email protected]> writes: > On Monday 20 January 2003 12:17, Balatoni Denes wrote: > > Hi! > > > > I never looked into this, but I would guess it's thread safe (glibc > > 2.2.2 or something with linuxthreads init), i use threads anyway. > > From the documentation, it is GLibc 2.2.3. The Glibc documentation does > not specifically state if the ARM port correctly handles threaded applications. > > You have not seen any problems while using threads (not Java threads)? > > If the C library is not rentrant, it can be difficult to find the problems. Threads work perfectly fine on the Zaurus. If they didn't, it wouldn't ship with libpthread. That said, far from all libc methods are reentrant. Many depend on statically allocated buffers for results (and often have an API that depends on that as well). This is however not platform specific but libc specific and in many cases, API specific (i.e no matter the libc / UN*X flavor the considerations are the same). I'm sure you all knew that already though. -- Eon Games - The Games Mobile Penguins Play Sales: [email protected] Support: [email protected] Bugs: [email protected] General: [email protected] Website address: http://eongames.com/ ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp