[6.0] It is impossible to debug the generated IntelliJ IDEA run configurations on Linux

[Jonathing]

I am completely unable to run debug in my IDE using the run configurations on Linux. After doing some shallow research, I'm led to believe that the run configurations are not handled in the same way as the JavaExec tasks are. This is because LWJGL complains about an unsupported JNI version, which I was able to debug as value 0x150000. This is not a real JNI version. If you are on Linux and are crashing on startup when the window opens on attempting to run debug on the generated client IDE run configuration, this is why.

There's no fix to the problem, but the workaround is to simply debug the runClient task itself. The server run config works fine in debug because the server does not use an LWJGL window.

My plan for FG7 is still to ditch IDE run configs in favor of the tasks themselves, so this is more of an informational issue in case others have had this same issue and don't know what's up.

See also:

• Crash cause by LWJGL: Unsupported JNI version libgdx/libgdx#7142

[Jonathing]

Here's a coredump for the curious: https://gist.github.com/Jonathing/d9caf15fcef028a9df124834fee1656e

and the JVM error log: https://gist.github.com/Jonathing/a0ff93d977d8275cf52a416b49bcecda

[Jonathing]

Closing as I won't fix this. ForgeGradle 7 will not re-implement IntelliJ XML run configs, and it is expected that the run tasks be used instead.

I am open to looking into ways of adding it to the drop-down menu for easier access on project import, but that doesn't change the fact that those entries would point to the Gradle tasks and not generated XML run configs.

I will pin this issue so that Linux users using ForgeGradle 6 are aware that I've encountered this problem.

[Jonathing]

Unpinning to make space for more important issues to track. I will need to remind myself (or @Fealtous) to add this as a note to ForgeGradle 6's documentation.