01-04-2021 04:17 AM
Hello,
I am trying to test some bare metal code using Vitis 2019.2 intalled on CentOS 8, but I am getting some jre error. I have used vitis application before but now when I try to open I get below error. How do I resolve this?
[kotrappa@loke Desktop]$ vitis
****** Xilinx Vitis Development Environment
****** Vitis v2019.2 (64-bit)
**** SW Build 2708876 on Wed Nov 6 21:40:25 MST 2019
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.
Launching Vitis with command /opt/Xilinx/Vitis/Vitis/2019.2/eclipse/lnx64.o/eclipse -vmargs -Xms64m -Xmx4G -Dorg.eclipse.swt.internal.gtk.cairoGraphics=false -Dosgi.configuration.area=@user.home/.Xilinx/Vitis/2019.2 --add-modules=ALL-SYSTEM --add-modules=jdk.incubator.httpclient --add-opens=java.base/java.nio=ALL-UNNAMED --add-opens=java.desktop/sun.swing=ALL-UNNAMED --add-opens=java.desktop/javax.swing=ALL-UNNAMED --add-opens=java.desktop/javax.swing.tree=ALL-UNNAMED --add-opens=java.desktop/javax.swing.plaf.basic=ALL-UNNAMED --add-opens=java.desktop/javax.swing.plaf.synth=ALL-UNNAMED --add-opens=java.desktop/com.sun.awt=ALL-UNNAMED --add-opens=java.desktop/sun.awt.X11=ALL-UNNAMED &
[kotrappa@loke Desktop]$ #
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f9a5af9cb60, pid=4132918, tid=4180806
#
# JRE version: Java(TM) SE Runtime Environment (9.0+11) (build 9.0.4+11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (9.0.4+11, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [libxerces-c-3.1.so+0x121b60] xercesc_3_1::XMLMutex::lock()+0x0
#
# 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 %e" (or dumping to /home/kotrappa/Desktop/core.4132918)
#
# An error report file with more information is saved as:
# /home/kotrappa/Desktop/hs_err_pid4132918.log
#
# If you would like to submit a bug report, please visit:
# http://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.
#
Any help would be gratefully received.
Regards,
Prasanna
01-04-2021 05:28 AM - edited 01-04-2021 05:29 AM
I think vitis was not previously closed properly, when I killed vitis process, and relaunched, it worked fine.
killall -9 vitis
01-04-2021 05:28 AM - edited 01-04-2021 05:29 AM
I think vitis was not previously closed properly, when I killed vitis process, and relaunched, it worked fine.
killall -9 vitis