Lines Matching +full:2 +full:x32 +full:- +full:bit
2 Uprobe-tracer: Uprobe-based Event Tracing
9 --------
13 Similar to the kprobe-event tracer, this doesn't need to be activated via
18 However unlike kprobe-event tracer, the uprobe event interface expects the
26 -------------------------
32 -:[GRP/][EVENT] : Clear uprobe or uretprobe event
49 +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*2)(\*3)
54 (x8/x16/x32/x64), "string" and bitfield are supported.
57 (\*2) this is useful for fetching a field of data structures.
59 events can access only user-space memory.
62 -----
63 Several types are supported for fetch-args. Uprobe tracer will access memory
66 in decimal ('s' and 'u') or hexadecimal ('x'). Without type casting, 'x32'
67 or 'x64' is used depends on the architecture (e.g. x86-32 uses x32, and
68 x86-64 uses x64).
69 String type is a special type, which fetches a "null-terminated" string from
71 Bitfield is another special type, which takes 3 parameters, bit-width, bit-
72 offset, and container-size (usually 32). The syntax is::
74 b<bit-width>@<bit-offset>/<container-size>
80 ---------------
86 --------------
98 echo '-:p_bash_0x4245c0' >> /sys/kernel/tracing/uprobe_events
112 # cat /proc/`pgrep zsh`/maps | grep /bin/zsh | grep r-xp
113 00400000-0048a000 r-xp 00000000 08:03 130904 /bin/zsh
114 # objdump -T /bin/zsh | grep -w zfree
126 .. note:: User has to explicitly calculate the offset of the probe-point
143 field:unsigned short common_type; offset:0; size:2; signed:0;
144 field:unsigned char common_flags; offset:2; size:1; signed:0;
153 print fmt: "(%lx) arg1=%lx arg2=%lx", REC->__probe_ip, REC->arg1, REC->arg2
177 # TASK-PID CPU# TIMESTAMP FUNCTION
179 zsh-24842 [006] 258544.995456: zfree_entry: (0x446420) arg1=446420 arg2=79
180 … zsh-24842 [007] 258545.000270: zfree_exit: (0x446540 <- 0x446420) arg1=446540 arg2=0
181 zsh-24842 [002] 258545.043929: zfree_entry: (0x446420) arg1=446420 arg2=79
182 … zsh-24842 [004] 258547.046129: zfree_exit: (0x446540 <- 0x446420) arg1=446540 arg2=0