• Home
Name Date Size #Lines LOC

..--

README.txtD03-May-2024601 129

jdwp.hD03-May-202415 KiB476237

jdwp_adb.ccD03-May-202412.3 KiB446273

jdwp_bits.hD03-May-20243.5 KiB12584

jdwp_constants.hD03-May-20248.5 KiB250176

jdwp_event.ccD03-May-202444.3 KiB1,387875

jdwp_event.hD03-May-20242.7 KiB11473

jdwp_expand_buf.ccD03-May-20244.5 KiB18997

jdwp_expand_buf.hD03-May-20242.2 KiB7124

jdwp_handler.ccD03-May-202459.9 KiB1,7631,181

jdwp_main.ccD03-May-202417.4 KiB620368

jdwp_priv.hD03-May-20242.4 KiB10549

jdwp_request.ccD03-May-20244.2 KiB186136

jdwp_socket.ccD03-May-202413.4 KiB503321

object_registry.ccD03-May-20247.3 KiB234183

object_registry.hD03-May-20244.3 KiB12767

README.txt

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