# g (continue debuggee or processing kernel packets) ### Command > g ### Syntax > g ### Description When the **HyperDbg** debugger is paused by [pause command](https://docs.hyperdbg.org/commands/debugging-commands/pause) or CTRL+C or CTRL+BREAK, you can continue debugging using this command. You can use this command in both **local** and **remote** debugging. ### Parameters None ### SDK To continue the debuggee, you need to use the following function in `libhyperdbg`: ```clike VOID hyperdbg_u_continue_debuggee(); ``` ### Remarks In remote debugging, [pause command](https://docs.hyperdbg.org/commands/debugging-commands/pause) or CTRL+C or CTRL+BREAK causes the target system to pause completely, and the target system halts. In local debugging, [pause command](https://docs.hyperdbg.org/commands/debugging-commands/pause) or CTRL+C or CTRL+BREAK causes the debugger to stop processing kernel and vmx packets (they won't stop working, we ignore the messages). Also, we don't save messages, so when you pause the debugger, then the logs from the events are ignored, and you can't process them in the future. ### Requirements None ### Related [pause (break to the debugger and pause processing kernel packets)](https://docs.hyperdbg.org/commands/debugging-commands/pause) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hyperdbg.org/commands/debugging-commands/g.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.