> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.2/user-guide/decompiler/interactive/cmd_variadic.md).

# Add/del variadic arguments

Hotkeys

**Numpad+**

Add variadic argument

**Numpad-**

Delete variadic argument

This command adds or removes an argument of a variadic call. It is impossible to detect the correct number of variadic arguments in all cases, and this command can be used to fix wrongly detected arguments. It is available only when the cursor is located on a call to a variadic function (like printf). The decompiler automatically detects the argument locations, the user can only increase or decrease their number.

This command is useful if the decompiler determines the number of arguments incorrectly. For example:

```
        printf("This is a test call: %d\n");
```

apparently lacks an argument. Pressing Numpad+ modifies it:

```
        printf("This is a test call: %d\n", v1);
```

If too many arguments are added to a variadic call, decompilation may [fail](/ida-9.2/user-guide/decompiler/failures.md). Three methods to correct this situation exist:

* undo the last action (hotkey Ctrl-Z)
* position the cursor on the wrongly modified call and press Numpad-
* or use [Edit, Other, Reset decompiler information](/ida-9.2/user-guide/decompiler/interactive.md#edit-other-reset-decompiler-information) to reset the forced varidic argument counts.

See also: [interactive operation](/ida-9.2/user-guide/decompiler/interactive.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/ida-9.2/user-guide/decompiler/interactive/cmd_variadic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.