| e9e1750a916cf602df722515736d21af63de1def |
|
23-Feb-2017 |
Sebastien Hertz <shertz@google.com> |
Cleanup construction of Value instances
Constructors are error-prone due to implicit conversion (char -> int,
...) so we introduce dedicated factory methods instead.
Also allows to remove useless casts (due to safer API).
Test: art/tools/run-jdwp-tests.sh --mode=host --variant=X64
Change-Id: I387eda20a2ff20c06c4a60afcdbfcd4e0392ca28
/external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/ClassType/InvokeMethodTest.java
|
| e1833aa2673d4f975ad35e7a39317feeea922fe1 |
|
23-Feb-2017 |
Sebastien Hertz <shertz@google.com> |
Fix warnings of JDWP tests
This CL fixes general warning issues:
- Adds missing @Override annotations
- Adds parameterized types for generic classes (List, Iterator, ...)
- Removes unused imports
- Removes declared method exceptions which are not thrown
- Adds @SuppressWarning annotations in debuggee classes (like when a
symbol is not used in the code but is accessed through debugger)
- Makes inner classes static when possible
More specific issues (related to design, ...) will be addressed in
separate CLs.
Test: art/tools/run-jdwp-tests.sh --mode=host --variant=X64
Change-Id: I83709f5d76b2a8c9268cd11dd7884982d5d06f2d
/external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/ClassType/InvokeMethodTest.java
|
| 684d91ef9b8c8022f19cc0d51598c2402303ed7c |
|
08-Oct-2014 |
Sebastien Hertz <shertz@google.com> |
Test event requests with LocationOnly modifier other than breakpoint
Checks we correctly support LocationOnly modifier for all possible
events other than breakpoint: single-step, exception, field access
and field modification events.
For exception and field access/modification events, we throw or
access/modify a field in two different methods. Then we request
corresponding event with a LocationOnly modifier related to the
second method only.
Since a location is {class id, method id, code index}, we'd need to
know exactly the code index where the event can be reported. As we
do not know the code (instructions and their respective code index),
we simply send an event request for each location. The common
testing code is in EventLocationEventTestCase class.
For single-step, we can't do the same because we can't request
multiple single-step events on the same thread. So we suspend in a
method, then single-step to the location of the last line of this
method.
Also move "resume debuggee" message into JDWPTestCase.resumeDebuggee
method so this is printed for all tests using it.
Change-Id: Id37df7560b588b8817c1dcf0ac29b1e5ebb91091
/external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/ClassType/InvokeMethodTest.java
|
| 5f0a23683aa603d8c50b6dd071a565821b76067b |
|
10-Dec-2011 |
Elliott Hughes <enh@google.com> |
Add harmony's jdwp tests.
Change-Id: I1c0e70cd9e07244fe422a4f77f3727b55ec28402
/external/apache-harmony/jdwp/src/test/java/org/apache/harmony/jpda/tests/jdwp/ClassType/InvokeMethodTest.java
|