# pause (break to the debugger and pause processing kernel packets)

### Command

> pause

### Syntax

> pause

### Description

On the remote system, this command halts the system and gives control of the remote system to the debugger. In local debugging, this command stops processing kernel and vmx packets and ignores them.

{% hint style="info" %}
You can unpause using the [g command](https://docs.hyperdbg.org/commands/debugging-commands/g).
{% endhint %}

### Parameters

None

### SDK

To pause the debuggee, you need to use the following function in `libhyperdbg`:

```clike
VOID
hyperdbg_u_pause_debuggee();
```

### Remarks

In remote debugging, pause command or CTRL+C or CTRL+BREAK causes the target system to pause completely, and the target system halts.

In local debugging, pause command 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.

Most of the time, this command is used in scripts after the '[sleep](https://docs.hyperdbg.org/commands/debugging-commands/sleep)' command to block further messages caused by triggering events.

### Requirements

None

### Related

[.script (run batch script commands)](https://docs.hyperdbg.org/commands/meta-commands/.script)

[g (continue debugging or processing kernel packets)](https://docs.hyperdbg.org/commands/debugging-commands/g)

[settings (configures different options and preferences)](https://docs.hyperdbg.org/commands/debugging-commands/settings)


---

# 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/pause.md?ask=<question>
```

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.