[uClibc 0001476]: Weird linking behaviour
bugs at busybox.net
bugs at busybox.net
Tue Apr 22 15:21:39 UTC 2008
The following issue requires your FEEDBACK.
======================================================================
http://busybox.net/bugs/view.php?id=1476
======================================================================
Reported By: sors
Assigned To: uClibc
======================================================================
Project: uClibc
Issue ID: 1476
Category: Posix Threads
Reproducibility: always
Severity: block
Priority: normal
Status: feedback
======================================================================
Date Submitted: 08-27-2007 02:46 PDT
Last Modified: 04-22-2008 08:21 PDT
======================================================================
Summary: Weird linking behaviour
Description:
I have an application that is linked dynamically to a shared lib, which
itself uses pthreads and is dynamically linked to the pthreads lib.
When a worker thread is created and started, the thread function is
called. But the main thread (which created the worker thread) never is
scheduled/run again! If the worker thread contains an infinitive loop, it
runs forever. If it exits (by using return) the whole process doesn't do
anything anymore.. It is blocked.
IF I link the pthreads lib to the application as well, the same code works
fine. The main thread and the worker thread are both scheduled as
expected.
======================================================================
----------------------------------------------------------------------
vapier - 12-30-07 12:29
----------------------------------------------------------------------
please post a small example application that exhibits the issue
----------------------------------------------------------------------
carmelo73 - 04-19-08 23:19
----------------------------------------------------------------------
Hi,
as Mike already asked, please provide us with a test case.
----------------------------------------------------------------------
carmelo73 - 04-22-08 08:21
----------------------------------------------------------------------
Hello,
I'm just thinking to a problem caused by wrong libgcc_so.
I suggest you to build ld.so with LD_DEBUG options enabled and run the
test case
again. We should be able to track the order and where the ld.so is
looking
for shared libraries.
Issue History
Date Modified Username Field Change
======================================================================
08-27-07 02:46 sors New Issue
08-27-07 02:46 sors Status new => assigned
08-27-07 02:46 sors Assigned To => uClibc
08-27-07 07:03 sors Issue Monitored: sors
10-05-07 04:04 sors Issue End Monitor: sors
12-30-07 12:29 vapier Note Added: 0003329
04-19-08 23:19 carmelo73 Note Added: 0006724
04-22-08 08:21 carmelo73 Note Added: 0006964
04-22-08 08:21 carmelo73 Status assigned => feedback
======================================================================
More information about the uClibc-cvs
mailing list