Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Bruce Momjian
Bruce Momjian wrote: > Manfred Spraul wrote: > > Jeroen Ruigrok/asmodai wrote: > > > > >-On [20030908 23:52], Peter Eisentraut ([EMAIL PROTECTED]) wrote: > > > > > > > > >>Why would FreeBSD have a "library of thread-safe libc functions" (libc_r) > > >>if the functions weren't thread-safe? I thi

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Bruce Momjian
Manfred Spraul wrote: > Jeroen Ruigrok/asmodai wrote: > > >-On [20030908 23:52], Peter Eisentraut ([EMAIL PROTECTED]) wrote: > > > > > >>Why would FreeBSD have a "library of thread-safe libc functions" (libc_r) > >>if the functions weren't thread-safe? I think the test is faulty. > >> > >>

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Manfred Spraul
Jeroen Ruigrok/asmodai wrote: -On [20030908 23:52], Peter Eisentraut ([EMAIL PROTECTED]) wrote: Why would FreeBSD have a "library of thread-safe libc functions" (libc_r) if the functions weren't thread-safe? I think the test is faulty. A thread-safe library has a per-thread errno value (i

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Jeroen Ruigrok/asmodai
-On [20030908 23:52], Peter Eisentraut ([EMAIL PROTECTED]) wrote: >Why would FreeBSD have a "library of thread-safe libc functions" (libc_r) >if the functions weren't thread-safe? I think the test is faulty. Having libc_r is not a guarantee that all functions of libc are represented in that libra

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Peter Eisentraut
Bruce Momjian writes: > > Both gethostbyname() and getpwuid() have no _r equivalents on > > FreeBSD-STABLE, ergo no thread-safe functions of these. > > So you don't have all the *_r functions, and your non-*_r functions > aren't thread-safe. Should we disable theading on FreeBSD? Seems so. Why

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Jeroen Ruigrok/asmodai
-On [20030908 18:52], Bruce Momjian ([EMAIL PROTECTED]) wrote: >So you don't have all the *_r functions, and your non-*_r functions >aren't thread-safe. Should we disable theading on FreeBSD? Seems so. Exactly. Most other threading works though. :) -- Jeroen Ruigrok van der Werven / asmodai

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Larry Rosenman
--On Monday, September 08, 2003 12:50:18 -0400 Bruce Momjian <[EMAIL PROTECTED]> wrote: Jeroen Ruigrok/asmodai wrote: -On [20030908 06:32], Bruce Momjian ([EMAIL PROTECTED]) wrote: >> Your gethostbyname() is _not_ thread-safe >> Your getpwuid() is _not_ thread-safe >> Your functions are _not_ a

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-08 Thread Bruce Momjian
Jeroen Ruigrok/asmodai wrote: > -On [20030908 06:32], Bruce Momjian ([EMAIL PROTECTED]) wrote: > >> Your gethostbyname() is _not_ thread-safe > >> Your getpwuid() is _not_ thread-safe > >> Your functions are _not_ all thread-safe > > > >Interesting. Do you have all the *_r files listed in thread.c

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-07 Thread Jeroen Ruigrok/asmodai
-On [20030908 06:32], Bruce Momjian ([EMAIL PROTECTED]) wrote: >> Your gethostbyname() is _not_ thread-safe >> Your getpwuid() is _not_ thread-safe >> Your functions are _not_ all thread-safe > >Interesting. Do you have all the *_r files listed in thread.c? I sure >hope so. I assume you used the

Re: [HACKERS] FreeBSD/i386 thread test

2003-09-07 Thread Bruce Momjian
Christopher Kings-Lynne wrote: > FreeBSD 4.8/i386: > > Your gethostbyname() is _not_ thread-safe > Your getpwuid() is _not_ thread-safe > Your functions are _not_ all thread-safe Interesting. Do you have all the *_r files listed in thread.c? I sure hope so. I assume you used the template threa

[HACKERS] FreeBSD/i386 thread test

2003-09-07 Thread Christopher Kings-Lynne
FreeBSD 4.8/i386: Your gethostbyname() is _not_ thread-safe Your getpwuid() is _not_ thread-safe Your functions are _not_ all thread-safe Chris - Original Message - From: "Bruce Momjian" <[EMAIL PROTECTED]> To: "Kurt Roeckx" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, Se