Application debugging method, apparatus, device, and medium
An application debugging method includes an interaction sub-system receiving identifiers of a plurality of application sub-modules that are input or selected by a user, creating debug sessions that are in a one-to-one correspondence with the plurality of application sub-modules, and then generating a plurality of debugging request messages based on the plurality of debug sessions. Each debugging request message is routed by the routing sub-system to an agent of an application sub-module requested to be debugged, to request debugging of a code block of the corresponding application sub-module.
1. A method, comprising:
receiving, by an interaction sub-system of an application debugging system, identifiers of a plurality of application sub-modules from a user, wherein a code block comprised in each of the application sub-modules is for implementing a function of an application;
creating, by the interaction sub-system, a plurality of debug sessions, wherein the debug sessions are in a one-to-one correspondence with the application sub-modules;
generating, by the interaction sub-system and based on the plurality of debug sessions, a plurality of debugging request messages by:
deleting standard message headers of a plurality of original debugging request messages; and
adding updated message headers to the plurality of original debugging request messages, wherein the updated message headers comprise a global debug session identifier and debug session identifiers; and
routing, by a routing sub-system of the application debugging system, the debugging request messages to agents of the application sub-modules to request debugging of code blocks.
2. The method of claim 1 , wherein each debug session comprises one of the debug session identifiers, and wherein generating, by the interaction sub-system and based on the plurality of debug sessions, the plurality of debugging request messages further comprises generating, by the interaction sub-system and based on the identifiers, the plurality of original debugging request messages.
3. The method of claim 2 , further comprising creating, by the interaction sub-system, a global debug session, wherein the global debug session comprises the global debug session identifier and corresponds to the plurality of debug sessions, and wherein adding the updated message headers comprises adding, by the interaction sub-system, the global debug session identifier to the plurality of original debugging request messages to obtain the plurality of debugging request messages.
4. The method of claim 1 , further comprising receiving, by the interaction sub-system, a plurality of debugging response messages, wherein the debugging response messages are in a one-to-one correspondence with debugging request messages.
5. The method of claim 1 , wherein before routing, by the routing sub-system of the application debugging system, each debugging request message to the agent of one of the application sub-modules, the application debugging method further comprises establishing, by the interaction sub-system, a persistent connection to the routing sub-system.
6. The method of claim 1 , further comprising discarding, by the interaction sub-system, a received debugging request message when a persistent connection to the routing sub-system fails to be established.
7. The method of claim 1 , further comprising disconnecting, by the interaction sub-system, a persistent connection to the routing sub-system when the plurality of debug sessions is closed.
8. The method of claim 1 , wherein deleting the standard message headers comprises deleting debug adapter protocol (DAP) headers of the original debugging request messages.
9. A method, comprising:
receiving a plurality of original debugging request messages, wherein each original debugging request message is for requesting to debug one of a plurality of application sub-modules of an application, and wherein a code block comprised in each application sub-module is for implementing a function of the application;
creating a plurality of debug sessions, wherein the debug sessions are in a one-to-one correspondence with the application sub-modules;
generating, based on debug session identifiers corresponding to the plurality of debug sessions and the plurality of original debugging request messages, a plurality of debugging request messages by:
deleting standard message headers of the plurality of original debugging request messages; and
adding updated message headers to the plurality of original debugging request messages, wherein the updated message headers comprise a global debug session identifier and the debug session identifiers; and
sending the plurality of debugging request messages.
10. The method of claim 9 , further comprising receiving a plurality of debugging response messages, wherein the debugging response messages are in a one-to-one correspondence with debugging request messages.
11. The method of claim 10 , further comprising:
deleting message headers of the plurality of debugging response messages, wherein the message headers comprise the debug session identifiers; and
adding the standard message headers to the plurality of debugging response messages.
12. The method of claim 9 , wherein before sending the plurality of debugging request messages, the method further comprises establishing a persistent connection to a routing sub-system.
13. The method of claim 9 , further comprising discarding a received debug request message when a persistent connection to a routing sub-system fails to be established.
14. The method of claim 9 , further comprising disconnecting a connection to the routing sub-system when the plurality of debug sessions is closed.
15. The method of claim 9 , wherein deleting the standard message headers comprises deleting debug adapter protocol (DAP) headers of the original debugging request messages.
16. A device, comprising:
a memory configured to store instructions; and
one or more processors coupled to the memory and configured to execute the instructions to:
receive identifiers of a plurality of application sub-modules from a user, wherein a code block comprised in each of the application sub-modules is for implementing a function of an application;
create a plurality of debug sessions, wherein the debug sessions are in a one-to-one correspondence with the application sub-modules; and
generate, based on the plurality of debug sessions, a plurality of debugging request messages, wherein each debugging request message is configured to be routed by a routing sub-system to an agent of one of the application sub-modules to request debugging of the code block corresponding to the one of the application sub-modules, and wherein generating the plurality of debugging request message comprises:
deleting standard message headers of a plurality of original debugging request messages; and
adding updated message headers to the plurality of original debugging request messages, wherein the updated message headers comprise a global debug session identifier and debug session identifiers.
17. The device of claim 16 , wherein the one or more processors are further configured to execute the instructions to generate the plurality of original debugging request messages.
18. The device of claim 17 , wherein the one or more processors are further configured to execute the instructions to:
create a global debug session, wherein the global debug session comprises the global debug session identifier and corresponds to the plurality of debug sessions; and
add the global debug session identifier to the plurality of original debug request messages to obtain the plurality of debugging request messages.
19. The device of claim 16 , wherein the one or more processors are further configured to execute the instructions to receive a plurality of debugging response messages, and wherein the debugging response messages are in a one-to-one correspondence with the debugging request messages.
20. The device of claim 16 , wherein the one or more processors are further configured to execute the instructions to delete debug adapter protocol (DAP) headers of the original debugging request messages.