Bug 81116 - undefined symbol error in /lib/tls/libthread_db.so.1
undefined symbol error in /lib/tls/libthread_db.so.1
Product: Red Hat Raw Hide
Classification: Retired
Component: glibc (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2003-01-04 20:49 EST by Nathan G. Grennan
Modified: 2007-04-18 12:49 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-15 17:43:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nathan G. Grennan 2003-01-04 20:49:27 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021216

Description of problem:
I run gdb xmms and I get the error below

dlopen failed on 'libthread_db.so.1' - /lib/tls/libthread_db.so.1: undefined
symbol: assert
GDB will not be able to debug pthreads.

This is after upgrading glibc to 2.3.1-30. Before I upgraded I had a similar
error about he same library in a different location and with a different
undefined symbol, which is why I upgraded.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install glibc-2.3.1-30
2. install gdb
3. install xmms
4. run startx
5. run gdb xmms

Actual Results:  dlopen failed on 'libthread_db.so.1' -
/lib/tls/libthread_db.so.1: undefined symbol: assert

Expected Results:  no error about the library and for it to be able to debu pthreads

Additional info:

This is a Phoebe system.
Comment 1 Jakub Jelinek 2003-01-07 11:24:17 EST
Fix just posted to libc-hacker, will be fixed in glibc-2.3.1-33.
Comment 2 Nathan G. Grennan 2003-01-14 05:09:05 EST

gdb xmms

dlopen failed on 'libthread_db.so.1' - /lib/tls/libthread_db.so.1: undefined
symbol: ps_get_thread_area
Comment 3 Nathan G. Grennan 2003-01-15 17:43:28 EST
Fixed with 2.3.1-36

Note You need to log in before you can comment on or make changes to this bug.