Latest LQ Deal: Latest LQ Deals
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 04-08-2005, 12:47 PM   #1
LQ Newbie
Registered: Apr 2005
Posts: 1

Rep: Reputation: 0
glibc 2.3.4 and pthreads

I read somewhere on the net that glibc 2.3.2 has a known threading issue where threads get livelocked for no reason. I discovered this after my program exhibited these symptoms. The stated cure for this problem was to upgrade to glibc 2.3.3 or higher. I upgraded to 2.3.4 but I still get the same problem. When the program livelocks, I attach gdb to it and do a backtrace and I find that the crucial thread is stuck during a call to pthread_cond_timedwait. The gdb frame entry for this method is as follows:
#1 0xf6fbecfc in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/

So my question is, if I upgraded to glibc 2.3.4, then why is this line saying GLIBC_2.3.2? Looking at /lib/tls, each of the .so's have version number 2.3.4.

Any idea what is going on there?


Old 04-23-2005, 03:53 AM   #2
Registered: Apr 2005
Distribution: LFS 5.0 and 6.1
Posts: 705

Rep: Reputation: 30
evidently some of the shared libraries did not get may need to move some of these's a pain I know but, .........
Old 04-26-2005, 12:13 PM   #3
LQ Newbie
Registered: Apr 2005
Posts: 3

Rep: Reputation: 0
libpthread- glibc 2.3.5-building

I'm porting glibc 2.3.5 to a new platform, one of our requirement is to build glibc static only, I mean -disable-shared. It means only "*.a" libraries will be created. Last time I built glibc 2.2.x where I could build all libs with -disable-shared flag in configure command, this time with glibc 2.3.5 while building modules such pwd, zic etc it throws error messages related pthread symbols undefined. Does it mean I cannot build pthread for static linking?

Example error messages
libc.a(setenv.o): In function `D.L_DL26':
setenv.o(.text+0x52c): undefined reference to `__pthread_mutex_unlock'
setenv.o(.text+0x530): undefined reference to `__pthread_mutex_unlock'
setenv.o(.text+0x54c): undefined reference to `__pthread_mutex_unlock'
setenv.o(.text+0x554): undefined reference to `__pthread_mutex_unlock'

libc.a(vfwprintf.o): In function `D.L_DL67':
vfwprintf.o(.text+0x1268): undefined reference to `_pthread_cleanup_push_defer'
vfwprintf.o(.text+0x126c): undefined reference to `_pthread_cleanup_push_defer'
vfwprintf.o(.text+0x12ec): undefined reference to `_pthread_cleanup_push_defer'
vfwprintf.o(.text+0x12f0): undefined reference to `_pthread_cleanup_push_defer'

Appreciate any valid feedback.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Default stack size on Linux/glibc/pthreads? rameshnj Linux - Newbie 3 11-03-2009 02:55 AM
problem installing glibc-2.3.2-4.80.i686, glibc-common-2.3.2-4.80.8.i386.rpm martianpackets Red Hat 8 05-01-2009 03:22 PM
Replacing glibc using linuxthreads for glibc using nptl (native positx thread library CestusGW Linux From Scratch 4 01-20-2005 07:26 AM
ncsd, glibc, and glibc-common conflicts during LAMP install beaker911 Linux - Software 0 12-30-2004 02:31 PM
glibc 2.3.2 => glibc 2.3.3 causes bash & syslog issues natetheros Red Hat 1 09-27-2004 01:35 AM > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 08:01 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration