Note https://bugs.eclipse.org/bugs/show_bug.cgi?id=400626#c48 in particular, which explains why the stack in https://bugs.webkit.org/show_bug.cgi?id=118396 (marked as a duplicate of the WebKit bug with the fix) is not the same as the stack in this report. I don't think that we know for sure that the upstream change will fix this issue, but the theory is that it's the underlying problem that leads to this report's crash since it was in the dump from gdb.
** Bug watch added: bugs.webkit.org/ #118396 https://bugs.webkit.org/show_bug.cgi?id=118396 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1160411 Title: SIGSEGV in runtime environment when starting Eclipse runtime workbench To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1160411/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
