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
In case of internal errors, the build process generates an error report
and no longer shows daunting stack traces. Instead, it fails with a
clear message that tells users how to proceed: inspect the error report
and, if unable to resolve the problem, file an issue with the error
report.
Inspired by HotSpot, the default filename for error reports is
`./svm_err_<timestamp>_pid<pid>.md`.
Copy file name to clipboardExpand all lines: substratevm/CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ This changelog summarizes major changes to GraalVM Native Image.
9
9
* (GR-41674) Class instanceOf and isAssignableFrom checks do need to make the checked type reachable.
10
10
* (GR-41100) Add support for `-XX:HeapDumpPath` to control where heap dumps are created.
11
11
* (GR-42148) Adjust build output to report types (primitives, classes, interfaces, and arrays) instead of classes and revise the output schema of `-H:BuildOutputJSONFile`.
12
+
* (GR-41912) The builder now generated reports for internal errors, which users can share when creating issues. By default, error reports follow the `svm_err_<timestamp>_pid<pid>.md` pattern and are created in the working directory. Use `-H:ErrorFile` to adjust the path or filename.
12
13
13
14
## Version 22.3.0
14
15
* (GR-35721) Remove old build output style and the `-H:±BuildOutputUseNewStyle` option.
@Option(help = "If an error occurs, save a build error report to this file [default: ./" + DEFAULT_ERROR_FILE_NAME + "] (%p replaced with pid, %t with timestamp).)")//
0 commit comments