Reduced accuracy in source positions when debugging native executables with latest GraalVM #30772
Comments
zakkak
added a commit
to zakkak/quarkus
that referenced
this issue
Feb 7, 2023
Instruct GraalVM / Mandrel to keep more accurate debug information about source locations when generating debug info for debugging and monitoring tools. This parameter may break compatibility with Truffle. Affected users should explicitly pass `-H:-TrackNodeSourcePosition` through `quarkus.native.additional-build-args` to override it. Closes: quarkusio#30772
zakkak
added a commit
to zakkak/quarkus
that referenced
this issue
Feb 7, 2023
Instruct GraalVM / Mandrel to keep more accurate debug information about source locations when generating debug info for debugging and monitoring tools. This parameter may break compatibility with Truffle. Affected users should explicitly pass `-H:-TrackNodeSourcePosition` through `quarkus.native.additional-build-args` to override it. Closes: quarkusio#30772
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
oracle/graal@67cc5c2 disables the
TrackNodeSourcePositionflag when generating debug info (-Dquarkus.native.debug.enabled). This results in less accurate mappings of native code to source code position (see Karm/mandrel-integration-tests#131).The change was motivated by the fact that
TrackNodeSourcePositionis a global flag of the compiler and enabling it by default when generating debug info clashes withIncludeNodeSourcePositionan option used for Truffle languages.That said, I was thinking about the following options:
Explicitly enable
-H:+TrackNodeSourcePositionin Quarkus since it doesn't officially support polyglot/truffle anyway. Users using these features will need to explicitly pass-H:-TrackNodeSourcePositionAccept the reduced accuracy by default and mention
-H:+TrackNodeSourcePositionin Quarkus docs.cc @galderz @geoand @gsmet
Expected behavior
Setting a breakpoint in gdb at line 71, e.g.
break Main.java:71, is expected to set the breakpoint at line 71.Actual behavior
Setting a breakpoint in gdb at line 71 results in a breakpoint at line 72.
How to Reproduce?
No response
Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: