| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
of latest glibc version
|
|
import glibc updates) while keeping the few bugfixes ... idea is to keep both old and new linuxthreads around so we can hack on the new version while delivering the old stable version to end users
|
|
|
|
|
|
Now GDB is happy and death events are reported as
[Thread 5126 (LWP 192) exited]
without GDB bailing out.
|
|
[Thread 1026 (Missing) exited]
messages again, while leaving the __linuxthreads_death_event()
call disabled, as it still breaks gdb.
|
|
Long time no see :)
It appears uClibc pthreads native debugging is broken w.r.t thread exit handling in
uClibc(at least on PPC). When debugging ex7, gdb(6.2.1) bails out as
soon as a thread exits. I found a comment in gdb that TD_DEATH handling was broken for
glibc 2.3.1, so I figured that maybe it was broken in uClibc also.
I added a #if 0 #endif in pthread_exit( see patch below) and then
gdb behaved again.
While looking into this I found a few differences( included in the patch)
between glibc and uClibc. Don't know if these makes a difference, but I leave that to
you to decide.
Jocke
|
|
from glibc 2.3. This should make threads much more efficient.
-Erik
|
|
glibc 2.1.3 and ported to work with uClibc by Stefan Soucek and Erik Andersen
(me). Stefan has hacked things up such that linuxthreads runs on MMU-less
systems (tested only on arm-nommu). Erik cleaned things up and made it work
properly as a shared library.
-Erik
|
