Age | Commit message (Collapse) | Author |
|
since we are going to support the two implementations of pthreads, we
again need to instead create symbolic links to use the proper version
of the file depending on the pthreads option chosen.
|
|
have to create symbolic links for 'semaphore.h' and 'pthread.h' which
will point to the proper pthreads directory. When we finish getting
NPTL working with uClibc, perhaps we can merge them, but a first glance
at the differences between the two does not make that very likely.
|
|
|
|
performance timers. If you want them included in the NPTL build, copy the
header from glibc into the 'libc/sysdeps/linux/<ARCH>' of your choice and
have fun.
|
|
|
|
|
|
bloated. *oink* *oink*
|
|
|
|
|
|
|
|
|
|
consult the 'README.NPTL' file.
|
|
|
|
placing the NPTL code under the top-level 'libpthread' directory.
Nothing compiles or even works at this point, so do not enable this
option.
|
|
|
|
$(LIBPTHREAD)
|
|
source tree.
|
|
|
|
a bit faster.
|
|
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
|
|
toplevel linuxthreads generic object files
|
|
|
|
running $(AR), and the toplevel $(AR) isnt invoked until subdirs have finished
|
|
updated
|
|
files get updated
|
|
options
|
|
|
|
Seperate out security features into a separate menu
|
|
-fstack-protector and -fno-stack-protector-all security
options
|
|
as the flags for all calls to 'as'
|
|
|
|
libthreaddb must not be stripped or gdb can't use it.
|
|
debugging not become confused,
|
|
adding cruft to include/sys/time.h. But also, there's no sense in
making changes like this until we decide how we're going to approach
the hidden symbol transition.
|
|
|
|
Hello!
Would the attached patch be acceptable (maybe instead of
__libc_gettimeofday using __gettimeofday)
We have some issues, see
http://bugs.gentoo.org/show_bug.cgi?id=65892
|
|
the utils using the uClibc-targeted toolchain.
|
|
The attached patch is an updated version of an earlier sent patch
It solves the problem that the target utils (ldconfig/ldd/iconv, readelf
is not handled, but can be easily added) are not built w/ the newly
created [S]crt[01].o files.
|
|
Corrects libpthread_db name (I do not know why libpthread_db.so uses
libpthread_db.so.1 instead of libpthread_db.so.$(MAJOR_VERSION) as soname)
Note by Jocke:
I don't known either but until then this is the right thing to do.
|
|
- adjust licensing terms of sources for crt*.o
- change the stat ABI to speed it up, matching changes in the kernel
- assorted bug-fixes, improvements and updates in the FR-V port
etc.
|
|
_dl_pagesize variable in ldso, so avoid aliasing.
-Erik
|
|
-Erik
|
|
|
|
Hi Erik,
I'm not sure why the NIOS support is not in uClibc -- perhaps the patch
was rejected or never submitted? In any case, I'm playing with some NIOS
stuff and created this patch against 0.9.26. The work was done by
Microtronix. I'm not sure who else contributed to it. It would be great
to have the NIOS support available in uClibc so developers don't have to
go searching for these bits.
Pete
|
|
instead, but we are not such a system and should not propagate such things.
|
|
A program that requests __pthread_sig_debug to be blocked will
self-deadlock when it requests a thread to be created, because the
debugger (rda or gdb) will never get the signal, so it won't wake up
the pthread manager as expected.
This patch fixes it.
|