TLS and multithreaded applications are known to not work with usermode
emulation.
In the end, it was an uninitialized stack allocated variable in libc
that was causing this problem
(http://sources.redhat.com/ml/libc-alpha/2006-09/msg00063.html).
Paul
Thanks,
Rafael
___
On 9/18/06, Paul Brook <[EMAIL PROTECTED]> wrote:
TLS and multithreaded applications are known to not work with usermode
emulation.
It looks like this is a memory corruption problem and the assert that
fails is just a coincidence!
I started to remove code from python to find what triggers the a
> What must be done for implementing TLS + multithread in qemu? Maybe I can
> help.
* Implement the TLS syscalls (futexes and the architecture specific bits).
There's a patch for clone() here: https://nowt.dyndns.org/patch.qemu_nptl
* Fix all the bits of qemu that aren't threadsafe (mainly the TB
TLS and multithreaded applications are known to not work with usermode
emulation.
We use python for compiling python modules inside scratchbox. So I
need to fix this or find a workaround (undef Py_HAVE_NATIVE_TLS?).
What must be done for implementing TLS + multithread in qemu? Maybe I can hel
On Monday 18 September 2006 21:05, Rafael Espíndola wrote:
> Running python 2.4 in qemu sometimes causes this assert
>
> Inconsistency detected by ld.so: rtld.c: 288: _dl_start_final:
> Assertion `info->l.l_tls_modid == 0' failed!
TLS and multithreaded applications are known to not work with userm
Running python 2.4 in qemu sometimes causes this assert
Inconsistency detected by ld.so: rtld.c: 288: _dl_start_final:
Assertion `info->l.l_tls_modid == 0' failed!
The same error is present in all versions tested (0.8.1, 0.8.2 and CVS).
I have been able to create a "small" ARM chroot that conta
