Well, for any running into this same issue with the unexplainable kernel spew, I've found a way around it. It seems if a fork sleeps for >= 1 microsecond (0.000001 seconds) immediately after creation, all proceeds normally (this value may vary). Any less, and it vomits. This would appear to have something to do with the EC2 hypervisor's inner workings, at the hardware or kernel level methinks.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/884181 Title: Running gdb causes "alignment check: 0000" error on 64-bit EC2 t1.micro instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884181/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
