Today got an update message in SW4 Eclipse to update Did that.
Now when trying to start "Debug" on an STM32MP1 board Exclipse just exits. The error is as follows. Debug files atttched.
Getting frustrated with the AC6/STM32MP1/Eclipse solution as a development environment ...Will go evaluate other platforms if the STM32MP1 environment and experience does not get stable soon.
OpenSTM32/plugins/com.st.stm32ide.mpu.externaltools.openocd.linux64_1.0.0.201902141520/resources/openocd-mpu/bin/openocd -d1 -f skeleton Debug (1).cfg -s /media/user/H3D1P2/Personal/2019/Projects/OpenSTM/Pangu/skeleton -s /media/user/H3D1P2/Tools/OpenSTM32/plugins/com.st.stm32ide.mpu.debug_1.1.0.201904120827/resources/openocd/st_scripts -c gdb_port 3333 -c tcl_port 6666 -c telnet_port 4444
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f4b99aa973d, pid=19624, tid=0x00007f4bdd45a700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_151-b12) (build 1.8.0_151-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.151-b12 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libgobject-2.0.so.0+0x3873d] g_type_check_instance_is_fundamentally_a+0xd
#
# 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:
# /media/user/H3D1P2/Tools/OpenSTM32/hs_err_pid19624.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.
