> > 2. I recently switched my target platform to Oxygen, and now my UI tests > > always segfault somewhere down the line: > > > > > # A fatal error has been detected by the Java Runtime Environment: > > > # > > > # SIGSEGV (0xb) at pc=0x00007f19ea78b510, pid=10922, > > > tid=0x00007f1b077af700 > > > # > > > # JRE version: Java(TM) SE Runtime Environment (8.0_102-b14) (build > > > 1.8.0_102-b14) > > > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.102-b14 mixed mode > > > linux-amd64 compressed oops) > > > # Problematic frame: > > > # C [libgdk-3.so.0+0x38510] gdk_test_simulate_button+0x0 > > > > It looks like this happens the first time SWTBot "clicks" on a Link > widget. > > But I don't have the faintest idea what to do about it. > > Can you share full stacktrace ? I haven't seen this one so a bit more > details is needed.
Oh, I forgot to link to the trace. Here it is: https://hudson.eclipse.org/mpc/job/epp-mpc-ci/ws/org.eclipse.epp.mpc.tests/hs_err_pid10922.log _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
