You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Produce separate .debug file when building with -g (or introduce new flag to make it optional)
Is your feature request related to a problem? Please describe.
In Quarkus objcopy is being used to split the debug info from the executable (which recently resulted into quarkusio/quarkus#13517). This seems like a good approach for other GraalVM users as well. This essentially allows users to deploy their application without the extra debug info, while still enabling them to copy the debug info over in case they need to debug their application.
Describe the solution you'd like.
Invoking native-image -g MyClass should generate an executable myclass without embedded debug info and another myclass.debug file containing the debug info.
Describe who do you think will benefit the most.
GraalVM users
developers of libraries and frameworks which depend on GraalVM
Describe alternatives you've considered.
The current alternative is to use objcopy --only-keep-debug and objcopy --strip-debug to split the binary after building it.
Additional context.
Quarkus issue that led to the creation of this issue: quarkusio/quarkus#13754
Express whether you'd like to help contributing this feature
Yes.
The text was updated successfully, but these errors were encountered:
Feature request
Produce separate
.debug
file when building with-g
(or introduce new flag to make it optional)Is your feature request related to a problem? Please describe.
In Quarkus
objcopy
is being used to split the debug info from the executable (which recently resulted into quarkusio/quarkus#13517). This seems like a good approach for other GraalVM users as well. This essentially allows users to deploy their application without the extra debug info, while still enabling them to copy the debug info over in case they need to debug their application.Describe the solution you'd like.
Invoking
native-image -g MyClass
should generate an executablemyclass
without embedded debug info and anothermyclass.debug
file containing the debug info.Describe who do you think will benefit the most.
Describe alternatives you've considered.
The current alternative is to use
objcopy --only-keep-debug
andobjcopy --strip-debug
to split the binary after building it.Additional context.
Quarkus issue that led to the creation of this issue: quarkusio/quarkus#13754
Express whether you'd like to help contributing this feature
Yes.
The text was updated successfully, but these errors were encountered: