-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P2
-
Affects Version/s: 26, 27
-
Component/s: infrastructure
-
master
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8374419 | 26.0.1 | Christoph Langer | P2 | Resolved | Fixed | master |
| JDK-8374211 | 26 | Christoph Langer | P2 | Resolved | Fixed | master |
I see this in Linux, but it may affect all or all non-Windows platforms.
I am no longer able to step into a function, and gdb does not seem to have debug information. On closer inspection, it appears we no longer copy debuginfo files into the bin directory.
Update: the workaround is to explicitly specify --with-native-debug-symbols=internal.
I am no longer able to step into a function, and gdb does not seem to have debug information. On closer inspection, it appears we no longer copy debuginfo files into the bin directory.
Update: the workaround is to explicitly specify --with-native-debug-symbols=internal.
- backported by
-
JDK-8374211 JDK-8351842 broke native debugging on Linux
-
- Resolved
-
-
JDK-8374419 JDK-8351842 broke native debugging on Linux
-
- Resolved
-
- caused by
-
JDK-8351842 Windows specific issues in combination of JEP 493 and --with-external-symbols-in-bundles=public
-
- Resolved
-
- links to
-
Commit(jdk26)
openjdk/jdk/6d9e91f8
-
Commit(master)
openjdk/jdk/b5ac8f83
-
Review(jdk26)
openjdk/jdk/28926
-
Review(master)
openjdk/jdk/28699
-
Review(master)
openjdk/jdk/28829
(3 links to)