GNOME Bugzilla – Bug 751159
A fatal error has been detected by the Java Runtime Environment
Last modified: 2015-06-21 20:50:42 UTC
Created attachment 305580 [details] log of the execution Seems that an old problem is back. When I run SwingSet2.jar using latest java-atk-wrapper, I received the following error. A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007faba35a1650, pid=14395, tid=140374990276352 # # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15) # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x39650] g_int_hash+0x0 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/vilmar/java-atk-wrapper/hs_err_pid14395.log # I'll attach a log of the execution and the error report file.
What triggered it? Did it happen after you switched orca by any chance. Could you please see bug 751053 and please let me know if this sounds like the problem you experienced.
Created attachment 305581 [details] error report file
(In reply to Magdalen Berns (irc magpie) from comment #1) > What triggered it? Did it happen after you switched orca by any chance. > The problem happens as soon I run SwingSet2.jar. No screen is shown. > Could you please see bug 751053 and please let me know if this sounds like > the problem you experienced. No, it is not the same problem.
(In reply to Jose Vilmar Estacio de Souza from comment #3) > (In reply to Magdalen Berns (irc magpie) from comment #1) > > What triggered it? Did it happen after you switched orca by any chance. > > > The problem happens as soon I run SwingSet2.jar. > No screen is shown. > > > Could you please see bug 751053 and please let me know if this sounds like > > the problem you experienced. > No, it is not the same problem. It seems like the same error message. Could you please upload /home/vilmar/java-atk-wrapper/hs_err_pid14395.log and can you let me know if you can reliably reproduce this each time you run SwingSet2 and whether orca is on or off when you do this?
There are two files attached in the bug. One file is a log with the command and the result and the second file is/home/vilmar/java-atk-wrapper/hs_err_pid14395.log. I can reproduce the bug all the time, with or without orca running.
(In reply to Jose Vilmar Estacio de Souza from comment #5) > There are two files attached in the bug. > One file is a log with the command and the result and the second file > is/home/vilmar/java-atk-wrapper/hs_err_pid14395.log. > > I can reproduce the bug all the time, with or without orca running. When did you last update the wrapper and when did you first notice this bug?
(In reply to Magdalen Berns (irc magpie) from comment #6) > > When did you last update the wrapper and when did you first notice this bug? today, 18/06/2015. Last time I tested with success was on sunday 14. I didn't repeat the tests until today. Do you want that I try to identify the commit that introduced the problem?
Created attachment 305623 [details] [review] possible fix (In reply to Jose Vilmar Estacio de Souza from comment #7) > (In reply to Magdalen Berns (irc magpie) from comment #6) > > > > When did you last update the wrapper and when did you first notice this bug? > > today, 18/06/2015. > Last time I tested with success was on sunday 14. I didn't repeat the tests > until today. > Do you want that I try to identify the commit that introduced the problem? I just am a bit puzzled as to why I can't recreate it but I have made changes so this might be it. In any case, I spotted an obvious bug whilst I was going through and pushed the commit to fix that either way. If you could pull the latest, clean everything and let me know if this is enough to help then that will be great. If that doesn't work I'll put my changes to one side and try to recreate it from there Thanks
Unless I have done something wrong, the problem remains. I pulled the latest from git, did a clean, autogen, make and make install. I'll attach the .log file.
Created attachment 305628 [details] new log file
(In reply to Jose Vilmar Estacio de Souza from comment #10) > Created attachment 305628 [details] > new log file (In reply to Jose Vilmar Estacio de Souza from comment #9) > Unless I have done something wrong, the problem remains. I pulled the latest > from git, did a clean, autogen, make and make install. That's odd. Have you done make distclean? Maybe check where you have some left over libraries hanging around from when you made with sudo. You can search for stray files (e.g. java-atk-wrapper.jar) with the following command: for f in $(locate java-atk-wrapper.jar); do dirname $f; done | uniq If that's not it then a trace would be useful.
(In reply to Magdalen Berns (irc magpie) from comment #11) > That's odd. Have you done make distclean? Maybe check where you have some > left over libraries hanging around from when you made with sudo. Yes, sudo make distclean and sudo git clean -fX > > You can search for stray files (e.g. java-atk-wrapper.jar) with the > following command: > > for f in $(locate java-atk-wrapper.jar); do dirname $f; done | uniq Only two files found. One file present where I compiled java-atk-wrapper and the other where it was installed. > > If that's not it then a trace would be useful. What can I do to get a trace?
(In reply to Jose Vilmar Estacio de Souza from comment #12) > What can I do to get a trace? Seems that I found the answer to my question! vilmar@jve:~/java-atk-wrapper[vilmar@jve java-atk-wrapper]$ coredumpctl gdb 16890 PID: [1;39m16890[0m (java) UID: 1000 (vilmar) GID: 1000 (vilmar) Signal: 6 (ABRT) Timestamp: Thu 2015-06-18 22:22:37 BRT (17min ago) Command Line: java -jar SwingSet2.jar Executable: [1;39m/usr/lib/jvm/java-7-jdk/jre/bin/java[0m Control Group: /user.slice/user-1000.slice/session-c2.scope Unit: session-c2.scope Slice: user-1000.slice Session: c2 Owner UID: 1000 (vilmar) Boot ID: d182ecf37a4a48cf882aa6da11dc7ed5 Machine ID: bb106a91062544e595ca975c0fb2973f Hostname: jve Coredump: /var/lib/systemd/coredump/core.java.1000.d182ecf37a4a48cf882aa6da11dc7ed5.16890.1434676957000000.lz4 Message: Process 16890 (java) of user 1000 dumped core. GNU gdb (GDB) 7.9.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/jvm/java-7-jdk/jre/bin/java...(no debugging symbols found)...done. [New LWP 16911] [New LWP 16891] [New LWP 16890] [New LWP 16903] [New LWP 16909] [New LWP 16902] [New LWP 16897] [New LWP 16893] [New LWP 16895] [New LWP 16892] [New LWP 16894] [New LWP 16896] [New LWP 16898] [New LWP 16899] [New LWP 16900] [New LWP 16904] [New LWP 16906] [New LWP 16910] [New LWP 16905] [New LWP 16908] [New LWP 16901] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `java -jar SwingSet2.jar'. Program terminated with signal SIGABRT, Aborted.
+ Trace 235186
(In reply to Jose Vilmar Estacio de Souza from comment #12) > (In reply to Magdalen Berns (irc magpie) from comment #11) > > That's odd. Have you done make distclean? Maybe check where you have some > > left over libraries hanging around from when you made with sudo. > Yes, sudo make distclean and sudo git clean -fX > > > > You can search for stray files (e.g. java-atk-wrapper.jar) with the > > following command: > > > > for f in $(locate java-atk-wrapper.jar); do dirname $f; done | uniq > Only two files found. One file present where I compiled java-atk-wrapper and > the other where it was installed. The files which were generated and installed should have been erased by doing a distclean. > > > > If that's not it then a trace would be useful. > What can I do to get a trace? I see you figured it out already. Thanks, I'll take a look!
Created attachment 305670 [details] [review] patch to fix bug Turned out it was me with some stray library files: I was able to reproduce and this patch seems to fix the issue for me. Please let me know if it's the same for you.
Seems that the patch fixed the problem but now I can not use SwingSet2.jar. Orca does not read nothing when I call SwingSet2.jar, as if the java-atk-wrapper was not installed. I'll investigate and file another bug reporting with more details.
Hi Jose, (In reply to Jose Vilmar Estacio de Souza from comment #16) > Seems that the patch fixed the problem but now I can not use SwingSet2.jar. > Orca does not read nothing when I call SwingSet2.jar, as if the > java-atk-wrapper was not installed. Thanks for issuing bug 751275 to follow up on this. I see you have confirmed that the problem is solved for you now - that is good news. I will close these two bugs (see bug 751183 for more information about the root cause of the issue :/) Please feel free to get in touch if you find any new problems. Thanks again for your help!