【问题标题】:New runtime configuration fails opening with error Failed to write core dump. Core dumps have been disabled新的运行时配置无法打开并出现错误无法写入核心转储。核心转储已被禁用
【发布时间】:2019-11-12 19:59:04
【问题描述】:

我正在尝试 Obeo Designer 社区 (https://wiki.eclipse.org/Sirius/Tutorials/DomainModelTutorial) 中提供的元建模工具

我可以生成代码,但是当我想测试元模型时,它会抛出我:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fff5767269d, pid=5954, tid=0x0000000000000307
#
# JRE version: Java(TM) SE Runtime Environment (8.0_211-b12) (build 1.8.0_211-b12)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.211-b12 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C  [libobjc.A.dylib+0x669d]  objc_msgSend+0x1d
#
# 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:
# /Users/nitishpatkar/Desktop/ObeoDesigner-Community.app/Contents/MacOS/hs_err_pid5954.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.
# 

我的 Mac 上有 java 版本 1.8.0_211。

有什么解决办法吗?

【问题讨论】:

    标签: eclipse ecore


    【解决方案1】:

    这似乎是由https://bugs.eclipse.org/bugs/show_bug.cgi?id=538377 引起的,该问题在最新版本的 Eclipse 中已修复,但存在于 Obeo Designer 中嵌入的版本中。

    从其中一个 cmets 看来,有一种解决方法:在启动配置中,您用于启动 Eclipse/Obeo Designer 的第二个实例(以测试您的元模型),在“参数”选项卡中添加“-nosplash”到“程序参数”。

    【讨论】:

      猜你喜欢
      • 2015-05-12
      • 2013-10-20
      • 1970-01-01
      • 2013-03-23
      • 1970-01-01
      • 1970-01-01
      • 2016-06-07
      • 2021-07-16
      相关资源
      最近更新 更多