• Home
Name Date Size #Lines LOC

..--

README.txtD03-May-2024601 129

jdwp.hD03-May-202417.5 KiB512240

jdwp_adb.ccD03-May-202414 KiB488309

jdwp_bits.hD03-May-20243.8 KiB13492

jdwp_constants.hD03-May-20248.5 KiB250176

jdwp_event.ccD03-May-202445 KiB1,379863

jdwp_event.hD03-May-20242.7 KiB11473

jdwp_expand_buf.ccD03-May-20244.6 KiB19299

jdwp_expand_buf.hD03-May-20242.2 KiB7124

jdwp_handler.ccD03-May-202458.4 KiB1,7151,157

jdwp_main.ccD03-May-202422.6 KiB785514

jdwp_options_test.ccD03-May-20242.4 KiB8041

jdwp_priv.hD03-May-20243.5 KiB12868

jdwp_request.ccD03-May-20244.2 KiB187136

jdwp_socket.ccD03-May-202414.8 KiB535336

object_registry.ccD03-May-20249.2 KiB288217

object_registry.hD03-May-20244.8 KiB14281

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