Probably my fault for the multiple email post (got stuck in the admin interface trap due to its size and I approved it without realizing that it had made it to the list already somehow).
Anyways.. I had a look at the thread_memory_from_self() function in the glib source code and I don't see anything that would suggest usage of SSE instructions (its a memory allocation function). There is a lot of use of the thread system though, so that could be the culprit. If you have a problem system you can test with, I would try building Glib with debugging information to see if you can get the actual source code line that is causing the crash. You could also do a disassembly dump at the instruction pointer EIP, to see what the actual instruction is, which also might provide some insight. Either the instruction was intended, but not supported on the problem system - which would mean glib may have been built for a platform that was too specific, or some sort of corruption is occurring. Looking at how glib got built (its build time options, thread support system, etc) might also be useful information. Hope that helps. Best regards, Element Green _______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev