[GR-54697] Implement debuginfo generation at image-runtime. #10522
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oracle-contributor-agreement
bot
added
the
OCA Verified
graalvmbot
force-pushed
the
doma/GR-54697
branch
from
6dfef33 to
a6101eb
Compare
|
Even if we don't get the GDB changes upstream in time this PR should be merged soon. The Debuginfo generation speedup due to parallelization plus the fix to make our DWARF5 work with GDB 16 or later justifies having this on master. |
graalvmbot
force-pushed
the
doma/GR-54697
branch
from
704775a to
b05b63f
Compare
graalvmbot
force-pushed
the
doma/GR-54697
branch
3 times, most recently
from
8866afc to
3e9f02a
Compare
graalvmbot
force-pushed
the
doma/GR-54697
branch
3 times, most recently
from
040181d to
ac8e19c
Compare
graalvmbot
force-pushed
the
doma/GR-54697
branch
2 times, most recently
from
f6cb0b8 to
da7b49d
Compare
|
@adinn this PR will likely be merged mid or end of next week. If you have any questions or comments, this would be a good time. cc @dominikmascherbauer |
1 task
graalvmbot
force-pushed
the
doma/GR-54697
branch
3 times, most recently
from
4006038 to
b3e78d8
Compare
olpaw
previously approved these changes
Jul 8, 2025
This is not required anymore as we now use GDB opaque types to refer to already at-build-time-defined types from the run-time debuginfo generator. |
graalvmbot
force-pushed
the
doma/GR-54697
branch
2 times, most recently
from
dddcdb2 to
3234927
Compare
graalvmbot
force-pushed
the
doma/GR-54697
branch
3 times, most recently
from
20dd01d to
c2ad2f0
Compare
…g information generation Implement the GDB JIT compilation interface Split off a shared debug information generator for use at image build-time and run-time Rework debug entries Parallelize debug information generation Add LocalVariableTable to SubstrateMethod Add tests for run-time debug information generation Refactor and rework gdb-debughelpers Make BFDNameProvider usable at image run-time Update Line section to DWARF5, fix bug when loading debug info in recent GDB versions (>= GDB 16) Add support for lazy deoptimization for frame unwinder and frame filter Implement opaque type resolution for runtime debug information in GDB Updates to CV debug information to be compatible with reworked debug information generation
graalvmbot
force-pushed
the
doma/GR-54697
branch
from
c2ad2f0 to
0a847fd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On Linux native-image supports generating images with dwarf-debuginfo. This allows advanced users to debug image execution with GDB.
Since debuginfo is generated as part of the image build process it is only providing debug support for the AOT compiled methods in an image. For methods that get compiled at image run-time (as part of truffle runtime compilation) there is currently no debuginfo available.
To fix this problem the process of generating debuginfo must also happen at image runtime whenever a new method gets compiled and is about to be registered in the run-time code-cache. This requires code that is currently only used at build-time (hosted) to be made usable also for inclusion in the image itself. The relevant parts of the hosted code need to be refactored as needed.
Once runtime-debuginfo is generated GDB needs to be notified about it. This needs to happen via the GDB JIT Interface. Note that it also required that GDB needs to be notified that run-time debuginfo is no more valid in case a run-time compiled method gets removed from the run-time code-cache (e.g. due to deoptimization).
The existing debuginfo testing needs to be extended to also test the run-time debuginfo generation.
Caveat: For GDB to be able to resolve type references from run-time debuginfo to AOT debuginfo, currently a modified version of GDB is required. https://github.com/dominikmascherbauer/binutils-gdb
We are working on getting the required changes upstream.