| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2041473 | 1.4.0 | Karen Kinnear | P2 | Closed | Fixed | beta |
When running the JCK tests on on build 17/18/19 I discovered that JCK tests
would fail with error code 134 intermittenly (instead of the normal 95)
The error code is 128+signal number ie SIGABRT
When running a particular JCK test standalone I always got the right code
95, only when running from within another java program (ie exec) do I
see this behavior
would fail with error code 134 intermittenly (instead of the normal 95)
The error code is 128+signal number ie SIGABRT
When running a particular JCK test standalone I always got the right code
95, only when running from within another java program (ie exec) do I
see this behavior
- backported by
-
JDK-2041473 getRuntime() exit fails on linux ladybird b17 onwards
-
- Closed
-
- duplicates
-
JDK-4427057 Linux: native2ascii crashes on reverse encoding Japanese manpages
-
- Closed
-
- relates to
-
-
- Closed
-