Summary: | In some cases debugger fails with org.eclipse.jdi.TimeoutException and the executed java-application is no longer responding | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Nobody - feel free to take it <nobody> |
Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | nobody, sarika.sinha |
Version: | 4.12 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 10 | ||
Whiteboard: | stalebug |
Description
Nobody - feel free to take it
2020-04-24 07:23:03 EDT
I am using Windows 10 Version 1909 (Build 18363.753) x64 My Eclipse-Version is: Eclipse IDE for Enterprise Java Developers. Version: 2019-06 (4.12.0) Build id: 20190614-1200 My Java-Version is: openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b06) OpenJDK 64-Bit Server VM GraalVM CE 20.0.0 (build 25.242-b06-jvmci-20.0-b02, mixed mode) Can reprodue the bug, But I don't have a fix for it. Unless VM sends a VM death or Disconnect Event Debugger waits for it. Thank you for your answer. So if I understand you correctly, is this a problem of the JVM or native debugger functionality and less of a problem of the Eclipse debugger? Two other thoughts came to mind: 1. In your opinion, is this a bug in the JVM implementation (here GraalVM) for which a report in the GitHub project (https://github.com/oracle/graal/) should be opened? 2. Would it make sense / be possible to expand the Eclipse debugger with a function that recognizes the problem I have described and, if possible, terminates the JVM or at least shows the user a more detailed / concrete message? (In reply to Alexander Guril from comment #3) > Thank you for your answer. So if I understand you correctly, is this a > problem of the JVM or native debugger functionality and less of a problem of > the Eclipse debugger? > > Two other thoughts came to mind: > 1. In your opinion, is this a bug in the JVM implementation (here GraalVM) > for which a report in the GitHub project (https://github.com/oracle/graal/) > should be opened? > > 2. Would it make sense / be possible to expand the Eclipse debugger with a > function that recognizes the problem I have described and, if possible, > terminates the JVM or at least shows the user a more detailed / concrete > message? Yes, we ahould report a problem to add an explanation and send an intermediate event for the debugger to be notified. In this case it is StackOverflow, it might be something else for a different scenario and Debugger is not supposed to guess, it should get the detailed events from the JVM and respond. Hi Sarika Sinha, How do we want to report the error to GraalVM? I lack any information about the actual JVM bug in order to create a reasonable issue. Do we want to coordinate in this regard? Do you want to create the issue on GitHub or do you provide me with the information I need to do it? This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |