On Mon, 3 Oct 2022 18:44:14 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
>> The main issues I set out to address are: >> >> - legacy Solaris references can be removed >> - add help with dealing with Windows core files, most of important of which >> is use of PATH to find the dlls referenced by the core file. >> - add help with dealing with macOS core files, most of important of which is >> using JAVA_HOME or DYLD_LIBRARY_PATH to find the dlls referenced by the core >> file. >> >> However, in the end it turned out to be a pretty substantial restructuring >> and rewrite. >> >> Here are links to the rendered new and old copies of the file: >> [new >> file](https://htmlpreview.github.io/?https://github.com/openjdk/jdk/blob/6778a202a855a534754c4b47a6cd99cb912869d3/src/jdk.hotspot.agent/doc/transported_core.html) >> [old >> file](https://htmlpreview.github.io/?https://github.com/openjdk/jdk/blob/master/src/jdk.hotspot.agent/doc/transported_core.html) > > Chris Plummer has updated the pull request incrementally with one additional > commit since the last revision: > > some additional clarification on linux and macos src/jdk.hotspot.agent/doc/transported_core.html line 44: > 42: OS version and libraries, and also having the same version of the JDK. It > also means having > 43: the OS libraries and JDK installed in the same locations on both > machines. However, often this isn't an option, > 44: and instead you need to include copies of the core dump machine's > libraries Perhaps, it can be rephrased as follows: ... instead you need to bring copies of the libraries and java installation from the machine where the core dump was produced to the debugger machine, and ... ------------- PR: https://git.openjdk.org/jdk/pull/10518
