RFR: 8317340: Windows builds are not reproducible if MS VS compiler install path differs
Andrew Leonard
aleonard at openjdk.org
Mon Oct 2 15:56:41 UTC 2023
On Mon, 2 Oct 2023 14:20:12 GMT, Andrew Leonard <aleonard at openjdk.org> wrote:
> > > What effect will this have on debugging?
> >
> >
> > Hi @erikj79 So this is the same as we pathmap the openjdk workspace source just above, in that we only do it when ALLOW_ABSOLUTE_PATHS_IN_OUTPUT is "false", which is for release builds. For "debug" builds it is "true" and no pathmap'ing occurs, see:
>
> Yes, I'm aware of that. I was just curious if you had tested and investigated the consequences of doing this when trying to debug a "release" build. I'm not against this change, but it would be good to understand any consequences.
@erikj79 So I started up a VS2022 debugging session for a java.exe process, and the vcruntime140 debugging information is loaded via the Microsoft Symbol Server anyway, same with debug src. Your VS2022 tools debugging source PATH for the VC tools is also pointing at your local VS2022 include folder.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/16008#issuecomment-1743277913
More information about the build-dev
mailing list