Another clue: I think it's signal handling related because (a) one of the values that gets smashed onto the stack is 0x11, which is SIGCHLD, and (b) if you use gdb to prevent SIGCHLD from being passed to the process (handle SIGCHLD nopass) it works.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1279620 Title: stack corruption running "go install launchpad.net/juju-core/..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1279620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
