Bug 85270 - dlsym is not thread safe
dlsym is not thread safe
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: glibc (Show other bugs)
phoebe
i686 Linux
high Severity high
: ---
: ---
Assigned To: Ulrich Drepper
Brian Brock
:
Depends On:
Blocks: 79578 84358
  Show dependency treegraph
 
Reported: 2003-02-26 23:26 EST by Ulrich Drepper
Modified: 2016-11-24 10:19 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-27 21:56:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Test program showing the crash (639 bytes, text/plain)
2003-02-26 23:27 EST, Ulrich Drepper
no flags Details
Patch to fix the problem (1.59 KB, patch)
2003-02-26 23:28 EST, Ulrich Drepper
no flags Details | Diff

  None (edit)
Description Ulrich Drepper 2003-02-26 23:26:20 EST
Description of problem:

Using dlsym in different threads at the same time can and will corrupt the stack
and cause a problem to crash if the dlsym() lookup failed.


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

glibc-2.3.2-2

How reproducible:

Run attached program.  Test code by Hui Huang from Sun.


Steps to Reproduce:
1. run the program, perhaps multiple times
2.
3.
    
Actual results:

crashes

Expected results:

no crash, no output

Additional info:
Comment 1 Ulrich Drepper 2003-02-26 23:27:36 EST
Created attachment 90392 [details]
Test program showing the crash

Test program written by Hui Huang.
Comment 2 Ulrich Drepper 2003-02-26 23:28:44 EST
Created attachment 90393 [details]
Patch to fix the problem

Patc relative to official CVS sources as of 2002-02-26T20:20:00-0800.
Comment 3 Ulrich Drepper 2003-02-26 23:56:18 EST
Waiting for fix to show up in rawhide.
Comment 4 Bill Nottingham 2003-02-27 12:39:22 EST
Fixed in 2.3.2-5.
Comment 5 Jay Turner 2003-02-27 21:56:05 EST
Fix confirmed in latest packages.

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