-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8318573: The nsk.share.jpda.SocketConnection should fail if socket was closed. #16280
Conversation
👋 Welcome back lmesnik! A progress list of the required criteria for merging this PR into |
Webrevs
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks reasonable.
Thanks,
Serguei
return null; | ||
e.printStackTrace(logger.getOutStream()); | ||
throw new Failure("Caught EOFException while reading an object from " + name + " connection." | ||
+ " Check if debugee process is exited (crashed, killed) before responded.\n\t"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: It feels like this line of error message can be improved but I do not have a suggestion at the moment.
@lmesnik This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 26 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
test/hotspot/jtreg/vmTestbase/nsk/share/jpda/SocketConnection.java
Outdated
Show resolved
Hide resolved
…java Co-authored-by: Chris Plummer <chris.plummer@oracle.com>
/integrate |
Going to push as commit 4cf195f.
Your commit was automatically rebased without conflicts. |
There are several failure with reason
"Cannot invoke "String.equals(Object)" because "" is null"
which really caused by reading the command from debugee via socket.
Like:
The command is null when socket fails with EOFException which usually means that debugee has been crashed/exited or killed by timeout handler.
However, it is not clear from the error log. So
https://bugs.openjdk.org/browse/JDK-8310940 has different problems with the same NPE symptom.
The fix update error handling to improve logging.
So output loos like:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/16280/head:pull/16280
$ git checkout pull/16280
Update a local copy of the PR:
$ git checkout pull/16280
$ git pull https://git.openjdk.org/jdk.git pull/16280/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 16280
View PR using the GUI difftool:
$ git pr show -t 16280
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/16280.diff
Webrev
Link to Webrev Comment