[HACKERS] Need NetBSD thread tester
I need someone running NetBSD to read the top of src/tools/test_thread_funcs.c and compile and run that function and report the results. Thanks. --- 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 Chris - Original Message - From: Bruce Momjian [EMAIL PROTECTED] To: Kurt Roeckx [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, September 04, 2003 6:07 AM Subject: Re: [HACKERS] Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...) Kurt Roeckx wrote: On Wed, Sep 03, 2003 at 03:36:53PM -0400, Bruce Momjian wrote: I would like every operating system that supports thread-safety to run this program and report back the results. On a Linux system with glibc 2.1: Your gethostbyname() is _not_ thread-safe Your getpwuid() is _not_ thread-safe Your functions are _not_ all thread-safe From a Linux system with libc5: Your gethostbyname() is _not_ thread-safe Your getpwuid() is _not_ thread-safe Your functions are _not_ all thread-safe Thanks. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Need NetBSD thread tester
--On Friday, September 12, 2003 12:18:52 -0400 Bruce Momjian [EMAIL PROTECTED] wrote: I need someone running NetBSD to read the top of src/tools/test_thread_funcs.c and compile and run that function and report the results. I have access to one NetBSD system on an Alpha: $ uname -a NetBSD milo.cirr.com 1.6.1_STABLE NetBSD 1.6.1_STABLE (MILO) #1: Sun Jun 1 20:44:15 CDT 2003 [EMAIL PROTECTED]:/rmt/.amd/egsner/root/work/eric/NetBSD-1.6/src/sys/arch/ alpha/compile/MILO alpha $ cc -O -o test_thread_funcs test_thread_funcs.c test_thread_funcs.c:27: pthread.h: No such file or directory $ cc -O -pthread -o test_thread_funcs test_thread_funcs.c cc: unrecognized option `-pthread' test_thread_funcs.c:27: pthread.h: No such file or directory $ cc -O -pthreads -o test_thread_funcs test_thread_funcs.c cc: unrecognized option `-pthreads' test_thread_funcs.c:27: pthread.h: No such file or directory $ locate pthread.h $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: [HACKERS] Need NetBSD thread tester
Larry Rosenman wrote: -- Start of PGP signed section. --On Friday, September 12, 2003 12:18:52 -0400 Bruce Momjian [EMAIL PROTECTED] wrote: I need someone running NetBSD to read the top of src/tools/test_thread_funcs.c and compile and run that function and report the results. I have access to one NetBSD system on an Alpha: $ uname -a NetBSD milo.cirr.com 1.6.1_STABLE NetBSD 1.6.1_STABLE (MILO) #1: Sun Jun 1 20:44:15 CDT 2003 [EMAIL PROTECTED]:/rmt/.amd/egsner/root/work/eric/NetBSD-1.6/src/sys/arch/ alpha/compile/MILO alpha $ cc -O -o test_thread_funcs test_thread_funcs.c test_thread_funcs.c:27: pthread.h: No such file or directory $ cc -O -pthread -o test_thread_funcs test_thread_funcs.c cc: unrecognized option `-pthread' test_thread_funcs.c:27: pthread.h: No such file or directory $ cc -O -pthreads -o test_thread_funcs test_thread_funcs.c cc: unrecognized option `-pthreads' test_thread_funcs.c:27: pthread.h: No such file or directory $ locate pthread.h Wow, that is strange. Someone else told me NetBSD supports threads, and doesn't need any special compile flags, but of course, it has to have pthread.h to support threads. NetBSD 1.6.1 is very current, so it isn't an old OS. Can you compile if you remove the pthread.h include? No special compile flags should be required. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Need NetBSD thread tester
--On Friday, September 12, 2003 13:03:33 -0400 Bruce Momjian [EMAIL PROTECTED] wrote: Larry Rosenman wrote: -- Start of PGP signed section. --On Friday, September 12, 2003 12:18:52 -0400 Bruce Momjian [EMAIL PROTECTED] wrote: I need someone running NetBSD to read the top of src/tools/test_thread_funcs.c and compile and run that function and report the results. I have access to one NetBSD system on an Alpha: $ uname -a NetBSD milo.cirr.com 1.6.1_STABLE NetBSD 1.6.1_STABLE (MILO) #1: Sun Jun 1 20:44:15 CDT 2003 [EMAIL PROTECTED]:/rmt/.amd/egsner/root/work/eric/NetBSD-1.6/src/sys/ar ch/ alpha/compile/MILO alpha $ cc -O -o test_thread_funcs test_thread_funcs.c test_thread_funcs.c:27: pthread.h: No such file or directory $ cc -O -pthread -o test_thread_funcs test_thread_funcs.c cc: unrecognized option `-pthread' test_thread_funcs.c:27: pthread.h: No such file or directory $ cc -O -pthreads -o test_thread_funcs test_thread_funcs.c cc: unrecognized option `-pthreads' test_thread_funcs.c:27: pthread.h: No such file or directory $ locate pthread.h Wow, that is strange. Someone else told me NetBSD supports threads, and doesn't need any special compile flags, but of course, it has to have pthread.h to support threads. NetBSD 1.6.1 is very current, so it isn't an old OS. Can you compile if you remove the pthread.h include? No special compile flags should be required. Nope.. $ vi test* $ cc -O -o test_thread_funcs test_thread_funcs.c test_thread_funcs.c: In function `main': test_thread_funcs.c:50: `pthread_t' undeclared (first use in this function) test_thread_funcs.c:50: (Each undeclared identifier is reported only once test_thread_funcs.c:50: for each function it appears in.) test_thread_funcs.c:50: parse error before `thread1' test_thread_funcs.c:59: `thread1' undeclared (first use in this function) test_thread_funcs.c:60: `thread2' undeclared (first use in this function) $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: [HACKERS] Need NetBSD thread tester
Larry Rosenman wrote: Wow, that is strange. Someone else told me NetBSD supports threads, and doesn't need any special compile flags, but of course, it has to have pthread.h to support threads. NetBSD 1.6.1 is very current, so it isn't an old OS. Can you compile if you remove the pthread.h include? No special compile flags should be required. Nope.. $ vi test* $ cc -O -o test_thread_funcs test_thread_funcs.c test_thread_funcs.c: In function `main': test_thread_funcs.c:50: `pthread_t' undeclared (first use in this function) test_thread_funcs.c:50: (Each undeclared identifier is reported only once test_thread_funcs.c:50: for each function it appears in.) test_thread_funcs.c:50: parse error before `thread1' test_thread_funcs.c:59: `thread1' undeclared (first use in this function) test_thread_funcs.c:60: `thread2' undeclared (first use in this function) $ There a pthrads package you have to install, (pkgsrc/devel/pth): http://groups.google.com/groups?q=netbsd+threads+pthread.hstart=30hl=enlr=ie=UTF-8selm=bhio3i%24cnp%241%40FreeBSD.csie.NCTU.edu.twrnum=35 Seems 2.0 will have native threads support. Now, how does this relate to libc's thread-safeness? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [HACKERS] Need NetBSD thread tester
--On Friday, September 12, 2003 13:30:38 -0400 Bruce Momjian [EMAIL PROTECTED] wrote: Larry Rosenman wrote: Wow, that is strange. Someone else told me NetBSD supports threads, and doesn't need any special compile flags, but of course, it has to have pthread.h to support threads. NetBSD 1.6.1 is very current, so it isn't an old OS. Can you compile if you remove the pthread.h include? No special compile flags should be required. Nope.. $ vi test* $ cc -O -o test_thread_funcs test_thread_funcs.c test_thread_funcs.c: In function `main': test_thread_funcs.c:50: `pthread_t' undeclared (first use in this function) test_thread_funcs.c:50: (Each undeclared identifier is reported only once test_thread_funcs.c:50: for each function it appears in.) test_thread_funcs.c:50: parse error before `thread1' test_thread_funcs.c:59: `thread1' undeclared (first use in this function) test_thread_funcs.c:60: `thread2' undeclared (first use in this function) $ There a pthrads package you have to install, (pkgsrc/devel/pth): http://groups.google.com/groups?q=netbsd+threads+pthread.hstart=30hl=e nlr=ie=UTF-8selm=bhio3i%24cnp%241%40FreeBSD.csie.NCTU.edu.twrnum=35 Seems 2.0 will have native threads support. Now, how does this relate to libc's thread-safeness? Bruce, I cc'd you on a note from milo.cirr.com's owner. That may shed some light. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 pgp0.pgp Description: PGP signature
Re: [HACKERS] Need NetBSD thread tester
quote who=Bruce Momjian Wow, that is strange. Someone else told me NetBSD supports threads, and doesn't need any special compile flags, but of course, it has to have pthread.h to support threads. NetBSD 1.6.1 is very current, so it isn't an old OS. NetBSD-1.6.1 doesn't have native thread. NetBSD-current has it though. Thomas T. Thai ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
