如何解决“检测到不一致:dl-lookup.c:111"问题? (Java结果127)错误? [英] How do I troubleshoot "Inconsistency detected: dl-lookup.c: 111" (Java Result 127) error?

问题描述

我目前正在尝试使用Maven为我正在开发的游戏构建Java项目.

I'm currently trying to build a Java project using Maven for a game I'm working on.

另一位用户最近推送到我们的存储库已经破坏了我的构建，但没有破坏其他用户.

A recent push to our repository by another user has broken the build for me, but not other users.

在最近的构建中，未对Pom.xml进行任何更改，并且我的Java环境保持一致.

No changes have been made the to Pom.xml in recent builds and my Java environment has remained consistent.

我在Ubuntu 18.04 LTS发行版上使用Java 8 OpenJDK(1.8.0_211).

I'm using Java 8 OpenJDK (1.8.0_211) on a Ubuntu 18.04 LTS distribution.

maven存储库能够成功编译，但是当我尝试使用预定的(mvn Integration-test -Pdesktop)构建执行代码时，会收到构建成功"，一些错误并且没有启动应用程序.

The maven repository is able to compile successfully, but when I try to execute the code using our predetermined (mvn integration-test -Pdesktop) build I receive a Build Success, some errors and no application launch.

我看过Linux论坛，但是找不到类似的案例.

I've looked on Linux forums, but have been unable to find similar cases.

普通Maven调试"选项未提供我认识到的问题的任何初始指示.

Normal Maven Debug options have not provided any initial indication of the problem that I recognise.

我看了几个Stack Overflow问题，包括 调试ld，"ld.so检测到不一致" ，但是不确定从何处开始以建议的方式提出评论，以及这是否适合我的情况.

I've looked at several Stack Overflow questions including debugging ld, "Inconsistency detected by ld.so" but am unsure where to begin with the comments suggested approaches and if this is viable for my case.

我看过Java错误代码127，该代码表明在我的CLASSPATH上找不到资源.这是正确的吗?如何确定似乎成功的构建中缺少的资源?

I've looked at the Java Error Code 127, which suggests that a resource cannot be found on my CLASSPATH. Is this correct and how do I identify the missing resource on what seems to be a successful build?

错误如下.

 [java] Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed!
[java] Java Result: 127

成功后，我希望该版本能够报告成功并启动游戏.在失败时，我原以为构建会报告失败，但是相反，我看到在没有启动LibGDX应用程序的情况下构建成功.

On success, I'm expecting the build to report a success and to launch the Game. On failure, I had expected the build to report a failure, but instead I'm seeing a build success without the launch of the LibGDX application.

该构建当前正在为其他平台上的用户运行.

The build is currently running for users on other platforms.

推荐答案

降级到OpenJDK 8

Downgrade to OpenJDK 8

我在带有Eclipse 2018-12(4.10.0)的Xubuntu 18.04中遇到了相同的问题.它工作正常，但可能是系统中的某些更新(或专门针对OpenJDK的更新)引发了此问题.此外，Gradle任务没有显示在Gradle窗口中.

I had the same problem in Xubuntu 18.04 with Eclipse 2018-12 (4.10.0). It was working fine, but probably some update in the system (or to OpenJDK specifically) started this problem. In addition Gradle Tasks weren't showing up in the Gradle Window.

我解决了删除软件包的问题:default-jre，default-jdk，default-jre-headless，default-jdk-headless，所有这些都指向" openjdk-11.

I solved the issue removing packages: default-jre, default-jdk, default-jre-headless, default-jdk-headless, all of them are "pointing at" openjdk-11.

然后我安装了软件包:openjdk-8-jre，openjdk-8-jdk，openjdk-8-jre-headless和openjdk-8-jdk-headless.

Then I installed packages: openjdk-8-jre, openjdk-8-jdk, openjdk-8-jre-headless and openjdk-8-jdk-headless.

将vm部分中的eclipse.ini更改为: -vm /usr/lib/jvm/java-8-openjdk-amd64/bin

Changed eclipse.ini in the vm section to: -vm /usr/lib/jvm/java-8-openjdk-amd64/bin

现在一切正常，并且Gradle任务再次显示.为了澄清，我也使用LibGDX.

And now everything is working fine, and Gradle tasks are showing again. To clarify, I'm also using LibGDX.

这篇关于如何解决“检测到不一致:dl-lookup.c:111"问题? (Java结果127)错误?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！