| Summary: | Evaluating empty varargs expression in debugger fails | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Ian Graham <igraham> | ||||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | igraham, sarika.sinha | ||||||
| Version: | 4.5.2 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | stalebug | ||||||||
| Attachments: |
|
||||||||
Created attachment 261101 [details]
Resulting dialog
I've also attached an image of the resulting dialog.
Depending on some syntactical circumstance I couldn't figured out, the message might be "java.lang.ArrayIndexOutOfBoundsException" instead of "-1". The problem seems to be with running Execute (Ctrl+U) when the empty invocation of the test method is selected. It occurs with Luna as well as Mars. Able to reproduce the bug. 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. |
Created attachment 261100 [details] Sample code to cause bug If you put a breakpoint in the first line of the main method in the provided example code and then debug it, you will find that if you evaluate the invocation of method() with no parameters, then you will get a strange error dialog.