Description of problem: Any java version fails on application (IBM ACS) use of libc.so.6 (???) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. java -jar acsbundle.jar 2. Select system 3. Start 5250 session 4. Fails Actual results: [hoffmanb@peabody ~]$ java -jar bin/acsbundle.jar Picked up JAVA_TOOL_OPTIONS: -Djdbc.drivers=com.ibm.as400.access.AS400JDBCDriver -Xmx2048m WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.ibm.eNetwork.HOD.acs.TabbedPane (file:/tmp/acs.jar_cache14447029094378103486.dir/75.dat) to constructor javax.swing.plaf.basic.LazyActionMap(java.lang.Class) WARNING: Please consider reporting this to the maintainers of com.ibm.eNetwork.HOD.acs.TabbedPane WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm_rec dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 dsp_protocol_open_node(): Could not open pcm device file /dev/dsptask/pcm2 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fc8f7a86b6a, pid=51410, tid=51436 # # JRE version: OpenJDK Runtime Environment 19.9 (14.0+36) (build 14+36) # Java VM: OpenJDK 64-Bit Server VM 19.9 (14+36, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64) # Problematic frame: # C [libc.so.6+0x9fb6a] __GI___strlen_sse2+0x2a # # Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/hoffmanb/core.51410) # # An error report file with more information is saved as: # /home/hoffmanb/hs_err_pid51410.log # # If you would like to submit a bug report, please visit: # https://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Aborted (core dumped) Expected results: 5250 session panel Additional info: This happened on F30 after a dnf upgrade last year. Still happens on F31. Happens with what ever version of Java I use: [hoffmanb@peabody ~]$ sudo alternatives --config java There are 8 programs which provide 'java'. Selection Command ----------------------------------------------- 1 java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-6.fc29.x86_64/jre/bin/java) 2 /usr/java/jdk1.8.0_162/jre/bin/java * 3 /usr/java/jdk-9.0.4/bin/java 4 /usr/java/jdk1.8.0_202-amd64/jre/bin/java 5 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.7.10-0.fc31.x86_64/bin/java) + 6 java-latest-openjdk.x86_64 (/usr/lib/jvm/java-14-openjdk-14.0.0.36-3.rolling.fc31.x86_64/bin/java) 7 /usr/java/jdk1.8.0_131/jre/bin/java 8 java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.fc31.x86_64/jre/bin/java)
Created attachment 1686331 [details] crash log
Passing invalid pointers to strlen is often the cause of such crashes e.g. "# C [libc.so.6+0x9fb6a] __GI___strlen_sse2+0x2a" There is not enough information here for us to diagnose what is happening. I'm going to pass this to the java-openjdk team to review the crash log and see if they recognize this as something they have seen before.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.