> The issue is fiddly but reproducible. All help in pinpointing the > problem source is appreciated. For the kernel bisect if you get stuck at a point it fails remember that point and then lie either yes/no to it working and carry on. If need be you can go back the other way. Another completely off the wall guess would be that your client code is causing gcc to generate something where it is using data which has ended up below the stack pointer and the timings have changed. Either through gcc bug or passing around the address of an object that is out of context. At that point a signal will rewrite the data in fun ways producing results like you describe. Alan -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
