| Anonymous | Login | Signup for a new account | 11-10-2008 11:18 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001476 | [uClibc] Posix Threads | block | always | 08-27-07 02:46 | 10-12-08 13:58 | ||||
| Reporter | sors | View Status | public | ||||||
| Assigned To | uClibc | ||||||||
| Priority | normal | Resolution | unable to reproduce | ||||||
| Status | closed | Product Version | 0.9.28 | ||||||
| Summary | 0001476: 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. |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |