Skip to content

Commit 12251e1

Browse files
committed
runtime_tools: fix dbg_guide link problem and one example descr.
1 parent 07d50b2 commit 12251e1

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

lib/runtime_tools/doc/guides/dbg_guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ limitations under the License.
1919
2020
%CopyrightEnd%
2121
-->
22-
# Tracing in Erlang with [**dbg**](`m:dbg`)
22+
# Tracing in Erlang with **dbg**
2323

2424
The [`dbg`](`m:dbg`) module in Erlang provides a text-based interface for tracing function calls, processes, ports, and messages. It simplifies the use of the underlying `trace:process/4`, `trace:port/4`, and `trace:function/4` BIFs (Built-In Functions). This guide will walk you through the basics of using `dbg` for your Erlang applications.
2525

@@ -346,8 +346,8 @@ will be used to match the arguments for the call:
346346
```
347347

348348
The first match specification matches when a function having two
349-
arguments is called. The second matches when a function with more than
350-
6 arguments is called.
349+
arguments is called. The second matches when a function, taking one
350+
atom as an argument, is called.
351351

352352
## Trace Sessions
353353

@@ -605,7 +605,7 @@ The pids will vary.
605605
* **[`dbg:stop_trace_client(Pid)`](`dbg:stop_trace_client/1`):** Shuts down
606606
the trace client `Pid`.
607607
608-
## Sequential Tracing (`seq_trace`)
608+
## Sequential Tracing
609609
610610
The `m:dbg` module is primarily targeted towards tracing through the
611611
`trace:process/4` function. It is sometimes desired to trace messages in a more

0 commit comments

Comments
 (0)