https://bugzilla.redhat.com/show_bug.cgi?id=1290784
--- Comment #15 from Christian Stadelmann <rhbz(a)genodeftest.de> ---
Created attachment 1198405
-->
https://bugzilla.redhat.com/attachment.cgi?id=1198405&action=edit
a full backtrace on java at "display_protocol_error"
(In reply to Christian Stadelmann from comment #13)
This bug now (in F25) triggers a crash in gnome-shell, see bug
#1330510 and
bug #1372311 for details.
Same on F24 too.
(In reply to Matthias Clasen from comment #14)
If this is reproducible, you could try to break on
display_protocol_error
where the EPROTO originates.
Yes, see attached logs. Steps I did:
0. run gdb from outside your gnome+wayland session, otherwise it will be killed
when your session goes down.
1. start eclipse in a gnome+wayland session (and make sure it is running with
wayland backend)
2. attach gdb to eclipse's child process named "java"
3. gdb: enable logging
4. gdb: disable handling of SIGSEGV because java is crazy and uses SIGSEGV for
normal operation: `handle SIGSEGV nostop noprint`
5. gdb: `break display_protocol_error`
6. gdb: continue
7. eclipse: right-click on any perspective button
8. gdb: `bt` and `t a a bt full`, then continue to the next hit. In fact I ran
these commands 3 times, the last one probably contains an error that the
wayland compositor is gone.
9. quit gdb, recover your gnome wayland session
--
You are receiving this mail because:
You are on the CC list for the bug.