-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GR-38651] Add -H:StripDebugInfo
and other tweaks for Debug Info.
#5691
Conversation
.../com.oracle.svm.hosted/src/com/oracle/svm/hosted/image/NativeImageDebugInfoStripFeature.java
Outdated
Show resolved
Hide resolved
ab58edb
to
e82c7dd
Compare
@@ -510,6 +521,16 @@ private void mangleType(ResolvedJavaType type) { | |||
} | |||
} | |||
|
|||
private void mangleType(UnresolvedJavaType type) { | |||
if (type.isArray()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't have a class loader for this unresolved type so I am not sure that we can guarantee that its name will not clash with a name for some valid resolved type. It might be safer to put all unresolved types into their own namespace to ensure this does not happen. That would also involve modifying the debug type info generation code to adopt the same namespace convention.
I'll leave that change for a follow-up PR once we can identify what other changes are required to ensure that debug info generator does not break if an unresolved type pops up as an element of the declaration closure for the runtime type set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks ok to push. I think we will need to do more work to ensure that unresolved types don't cause any grief during debug info generation.
-H:StripDebugInfo
and other tweaks for Debug Info.-H:StripDebugInfo
and other tweaks for Debug Info.
c0ef533
to
15799f3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New changes still looking good
15799f3
to
995db62
Compare
substratevm/src/com.oracle.objectfile/src/com/oracle/objectfile/debugentry/DebugInfoBase.java
Show resolved
Hide resolved
...tevm/src/com.oracle.objectfile/src/com/oracle/objectfile/elf/dwarf/DwarfInfoSectionImpl.java
Show resolved
Hide resolved
@christianhaeubl to switch our debuginfo implementation to the new improved one by RedHat @fniephaus found an issue when it is used in combination with G1 GC. Commit 058563c contains our attempt to fix the problem. Please let us know if this looks legit to you. The code is question is creating dwarf expressions (small dwarf sub-programms that get interpreted by gdb to resolve oop references) based on the object representation for the image that gets built. |
@olpaw thanks, looks good to me. |
41f2371
to
bd50635
Compare
66d1486
to
6f85813
Compare
6f85813
to
4b240bd
Compare
4b240bd
to
fc40db3
Compare
No description provided.