On Wednesday 15 October 2008 08:43:47 Chase N Douglas wrote: > -----Bernhard Reutner-Fischer <[EMAIL PROTECTED]> wrote: ----- > > >On Mon, Oct 06, 2008 at 04:14:27PM -0400, Chase Douglas wrote: > >> On Oct 6, 2008, at 6:04 AM, Fathi Boudra wrote: > >>> Hi, > >>> > >>> ping. > >>> > >>> Any comments from people who care about thread ? > >>> > >>> As a reminder: > >>> - http://busybox.net/bugs/view.php?id=4994 > >>> - http://uclibc.org/lists/uclibc/2008-March/019187.html > >>> > >>> It could be nice to take a look before 0.9.30 release. > >> > >> Just to be clear, both of these tackle the same issue, but the first > >> should cover all cases, while the second is specific to malloc-standard > >> and does not cover the pthreads_atfork mutex. > > > >This patch (which went in as r23660) broke > >- no threads > >- malloc debug > > Do you have any information on how the patch broke these two scenarios? > Were they compilation errors, or runtime errors? What malloc stack(s) > broke? I have not been able to reproduce the issues myself, but I have been > running an older version of uClibc, not 0.9.30-rc2.
Building armv4l oabi, init=/bin/bash failed with an error from bash saying that xmalloc tried to allocate a couple hundred bytes and wound up allocating 0 bytes. (At which point it exited and the kernel paniced because it was PID 1.) If you'd like to reproduce the problem, download my Firmware Linux build script from http://landley.net/hg/firmware/archive/tip.tar.gz, run "./build.sh armv4l", and then "cd build/system-image-armv4l" and "./run-emulator.sh". (That last step assumes you have qemu 0.9.1 installed.) It's currently configured to use stock -rc2, and I'll probably leave it that way until -rc3 (or the final version) comes out since this only breaks arm and its' easy for me to fix locally with a reversion patch. Rob _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
