diff options
| author | Kartik Agaram <vc@akkartik.com> | 2019-04-28 01:00:24 -0700 |
|---|---|---|
| committer | Kartik Agaram <vc@akkartik.com> | 2019-04-28 01:10:17 -0700 |
| commit | 02684e8d7cb5292867ebcdea06879b94ba63aef4 (patch) | |
| tree | fcd9005dea315966f9f611b9739f1d6e44b1f694 /subx/Readme.md | |
| parent | ffe66972277c856f33e349b3d1fd1b2a6b5bfa2a (diff) | |
| download | mu-02684e8d7cb5292867ebcdea06879b94ba63aef4.tar.gz | |
5133 - show instruction source in trace
It's a little hacky in some corner cases. In particular, if debug information isn't available the trace will contain duplicated lines. This is because I don't want the core trace lines all my tests rely on (introduced in the 'vm' layer) to have to know about debug info (introduced in the 'labels' and 'debug' layers). Thanks Charles Saternos for the feedback and suggestion!
Diffstat (limited to 'subx/Readme.md')
| -rw-r--r-- | subx/Readme.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/subx/Readme.md b/subx/Readme.md index 15cb9972..e8e4ad6d 100644 --- a/subx/Readme.md +++ b/subx/Readme.md @@ -43,6 +43,7 @@ Emulated runs generate a trace that permits [time-travel debugging](https://gith ```sh $ ./subx --debug translate examples/factorial.subx -o examples/factorial saving address->label information to 'labels' + saving address->source information to 'source_lines' $ ./subx --debug --trace run examples/factorial saving trace to 'last_run' $ ../browse_trace/browse_trace last_run # text-mode debugger UI |