Skip to content

options.md

Latest commit

 

History

History
127 lines (75 loc) · 2.32 KB

options.md

File metadata and controls

127 lines (75 loc) · 2.32 KB

Pinpoint Command-Line Options

This document describes all supported command-line options for the pintool. Options are passed as Intel Pin knobs using the -pintool namespace and must be specified before the -- separator.

Output

-o <path>

Specifies the output file used by the pintool. All generated traces, logs, and statistics are written to this file.

  • Default: out

Routine Selection

-f <list>

Restricts instrumentation to a specific set of routines.

  • The value is a semicolon-separated list of routine names
  • If empty or omitted, all routines are instrumented

Example:

-f main;malloc;free

Instruction Filtering

-skip <n>

Skips the first n dynamically executed instructions before instrumentation begins.

  • Useful for ignoring startup and initialization code
  • Default: 0

Instruction Tracing

-print_ins {0|1}

Controls whether executed instructions are printed.

  • 0 — Disabled
  • 1 — Enabled
  • Default: 1

-indent {0|1|2}

Controls indentation of printed trace entries based on call depth.

Value Description
0 No indentation
1 Indent using spaces
2 Indent using tabs
  • Default: 1

Opcode Analysis

-count_opcodes {0|1}

Enables counting of executed opcodes and reports aggregate statistics.

  • 0 — Disabled
  • 1 — Enabled
  • Default: 0

Memory and Register Tracking

-print_memwrites {0|1}

Logs memory write operations performed by instructions.

  • 0 — Disabled
  • 1 — Enabled
  • Default: 1

-print_regwrites {0|1}

Logs architectural register write operations.

  • 0 — Disabled
  • 1 — Enabled
  • Default: 1

System and ABI Visibility

-print_syscalls {0|1}

Enables logging of system call invocations.

  • 0 — Disabled
  • 1 — Enabled
  • Default: 0

-print_args {0|1}

Prints function argument registers at routine entry, according to the platform ABI.

  • 0 — Disabled
  • 1 — Enabled
  • Default: 0

Notes

  • Enabling instruction-level printing and memory/register tracking may significantly increase trace file size.
  • Combining -skip with routine filtering (-f) can help focus the analysis on relevant execution phases.