-
Bug
-
Resolution: Fixed
-
P4
-
11, 14, 15
-
b06
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8238242 | 14.0.2 | Christoph Langer | P4 | Resolved | Fixed | b01 |
| JDK-8238485 | 14.0.1 | Christoph Langer | P4 | Resolved | Fixed | b03 |
| JDK-8246562 | 13.0.4 | Christoph Langer | P4 | Resolved | Fixed | b04 |
| JDK-8238771 | 11.0.7 | Christoph Langer | P4 | Resolved | Fixed | b03 |
The configure option --with-native-debug-symbols controls the way whether native debug symbol information is generated during the build and where it is stored. Possible options are no debug symbols at all, stored inside the binaries, stored in external files and stored externally and zipped.
Since the only known way to have debug symbols on Windows are external .pdb files, the option --with-native-debug-symbols=internal does not make sense and should be rejected by configure.
Since the only known way to have debug symbols on Windows are external .pdb files, the option --with-native-debug-symbols=internal does not make sense and should be rejected by configure.
- backported by
-
JDK-8238242 Support for configure option --with-native-debug-symbols=internal is impossible on Windows
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-