On Mon, 19 Aug 2013, Element Green wrote:
I've often found that the glib memory slice subsystem can be sensitive to memory corruption. It could be that there is some other unrelated memory corruption going on which is causing this.
In that case I'd expect a segfault before anything could intrude on instruction space. File corruption seems a more likely suspect.
I still think GCC is simply generating an instruction that the build system knows about and the host doesn't, though it's hard to imagine what that would be (pclmulqdq?). Obviously, it would help enormously if we knew exactly what triggered the SIGILL.
_______________________________________________ fluid-dev mailing list fluid-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/fluid-dev
