You can open the debug info in our implementation when run the unit test. Pass property jpda.settings.debuggeeAgentExtraOptions to vm, such as:
-Djpda.settings.debuggeeAgentExtraOptions=trace=DATA The current implementation uses the following trace message types you can open: CMD - JDWP commands execution PACK - JDWP packets read/write operations DATA - JDWP packets parsing and composing EVENT - JDWP events tracing MEM - memory allocation and de-allocation MAP - object and class ID mapping THRD - thread operations MON - thread synchronization and monitor operations PROG - program flow tracing FUNC- agent functions entry/exit JVMTI - JVMTI calls tracing UTIL - auxiliary utility messages LOG - arbitrary log messages INFO - information and warning messages ERROR - error messages 2008/3/20, Regis <[EMAIL PROTECTED]>: > Yes, most normal code path is tested, maybe we should pay more attentions > on error and exception cases. > > And i found that it's hard to test error case in native > code using java unit test, such as read/write socket or allocate/cop > memory . > > Any thoughts/suggestions about this? > > Sean Qiu wrote: > > Hi, all > > > > I have run our unit test for jdwp to get a coverage report. > > The report is attained through gcov > > lcov is used to get a more readable html report. > > > > The good news is the report indicate that our jdwp implementation is > > mostly covered and tested.I raise a jira[1] to upload the report. > > If someone else is also interested in it, i can summarize it here or > > to our wiki. > > > > [1] https://issues.apache.org/jira/browse/HARMONY-5619 > > > -- Best Regards Sean, Xiao Xia Qiu China Software Development Lab, IBM
