File: 202built-in-variables-args.d

package info (click to toggle)
dtrace 2.0.5-1
  • links: PTS
  • area: main
  • in suites: sid
  • size: 24,408 kB
  • sloc: ansic: 61,247; sh: 17,997; asm: 1,717; lex: 947; awk: 754; yacc: 695; perl: 37; sed: 17; makefile: 15
file content (35 lines) | stat: -rwxr-xr-x 995 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
/*
 * Linux DTrace
 * Copyright (c) 2025, Oracle and/or its affiliates. All rights reserved.
 * Licensed under the Universal Permissive License v 1.0 as shown at
 * http://oss.oracle.com/licenses/upl.
 */

#!/usr/sbin/dtrace -s

/*
 *  SYNOPSIS
 *    sudo ./202built-in-variables-args.d
 *
 *  DESCRIPTION
 *    A probe's arguments can be accessed through the built-in
 *    variables arg0, arg1, arg2, etc.  These are all signed,
 *    64-bit integers, whose meanings depend on the probe.
 *
 *    Some probes have typed arguments args[0], args[1], args[2],
 *    etc.  To see the types, use "dtrace -lvn $probe".  Their
 *    meanings are described in the documentation.
 *
 *    When arguments are typed, they may also be reordered.
 *    So there may be no correspondence between, say, arg0
 *    and args[0].
 *
 *    Typically, it is better to use the typed args[] when
 *    the probe has them.
 */

syscall::write:entry
{
	printf("Write %d bytes to fd %d\n", args[2], arg0);
	exit(0);
}