Home | History | Annotate | only in /art/runtime/jdwp
Up to higher level directory
NameDateSize
jdwp.h10-Mar-201515K
jdwp_adb.cc10-Mar-201512.3K
jdwp_bits.h10-Mar-20153.5K
jdwp_constants.h16-Dec-20148.5K
jdwp_event.cc10-Mar-201544.3K
jdwp_event.h16-Dec-20142.7K
jdwp_expand_buf.cc16-Dec-20144.5K
jdwp_expand_buf.h16-Dec-20142.2K
jdwp_handler.cc10-Mar-201559.9K
jdwp_main.cc10-Mar-201517.4K
jdwp_priv.h16-Dec-20142.4K
jdwp_request.cc16-Dec-20144.2K
jdwp_socket.cc10-Mar-201513.4K
object_registry.cc10-Mar-20157.3K
object_registry.h10-Mar-20154.3K
README.txt16-Dec-2014601

README.txt

      1 Java Debug Wire Protocol support
      2 
      3 This is a reasonably complete implementation, but only messages that are
      4 actually generated by debuggers have been implemented.  The reasoning
      5 behind this is that it's better to leave a call unimplemented than have
      6 something that appears implemented but has never been tested.
      7 
      8 An attempt has been made to keep the JDWP implementation distinct from the
      9 runtime, so that the code might be useful in other projects. Once you get
     10 multiple simultaneous events and debugger requests with thread suspension
     11 bouncing around, though, it's difficult to keep things "generic".
     12