before taking this to the gnome folks I was trying rule out a connection between glibc and the above mentioned gcc bug by recompiling glibc with gcc 3.4 (because __generic_mutex_lock DOES use some inline asm code and could match the gcc bug). However, that seems to be beyond my current skills. After spending hours on getting glibc compiled from the source debs, I spent another few hours making my system boot again. So, if anybody here with more xp tinkering with glibc could help out here, trying to narrow this down, that would be much appreciated.
-- get libpthread assertion on multicore CPU https://launchpad.net/bugs/60708 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
