Skip to content

Commit 257c1d5

Browse files
committed
Update v3/docs/opt-trace-format.md
1 parent 672804b commit 257c1d5

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

v3/docs/opt-trace-format.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -483,7 +483,8 @@ which corresponds to the Python object `(1, c)`.
483483
The ability to put "REF" objects inside of heap objects enables an arbitrary object graph to be
484484
represented in the execution trace.
485485

486-
## stdout output
486+
487+
## Capturing `stdout` Output
487488

488489
The `stdout` field in an execution point object represents the sum total of all output sent to stdout
489490
so far during execution. For example, given this program:
@@ -558,7 +559,7 @@ subsequent execution point. If we grep for `stdout` in the trace, we see the fol
558559
```
559560

560561
This isn't rocket science; but just be aware that `stdout` contains the cumulative contents of the stdout
561-
buffer up to that execution point, not only what's just been printed by the last executed line.
562+
buffer up to that execution point, not only what's been printed by the most recently executed line.
562563

563564

564565
## Function Stack Frames

0 commit comments

Comments
 (0)