diff options
| author | Björn Gustavsson <[email protected]> | 2011-03-08 11:12:56 +0100 |
|---|---|---|
| committer | Björn Gustavsson <[email protected]> | 2011-08-18 10:00:30 +0200 |
| commit | c67dcea4a123ad7871040ec991674533953f8c48 (patch) | |
| tree | 62b0d670e0c09780561c0529dca0e65b4b5e2d50 /lib/debugger | |
| parent | 8799bbf2c0f644008828fb1000b72fafb3fa58ec (diff) | |
| download | otp-c67dcea4a123ad7871040ec991674533953f8c48.tar.gz otp-c67dcea4a123ad7871040ec991674533953f8c48.tar.bz2 otp-c67dcea4a123ad7871040ec991674533953f8c48.zip | |
Update examples in the documentation to include line numbers
Diffstat (limited to 'lib/debugger')
| -rw-r--r-- | lib/debugger/doc/src/debugger_chapter.xml | 24 |
1 files changed, 11 insertions, 13 deletions
diff --git a/lib/debugger/doc/src/debugger_chapter.xml b/lib/debugger/doc/src/debugger_chapter.xml index 1f5d4dd5ff..67e95cd083 100644 --- a/lib/debugger/doc/src/debugger_chapter.xml +++ b/lib/debugger/doc/src/debugger_chapter.xml @@ -254,19 +254,17 @@ c_break(Bindings) -> used, for example, if an error occurs:</p> <pre> 1> <input>catch a+1.</input> -{'EXIT',{badarith,[{erlang,'+',[a,1]}, - {erl_eval,do_apply,5}, - {erl_eval,expr,5}, - {shell,exprs,6}, - {shell,eval_exprs,6}, - {shell,eval_loop,3}]}}</pre> - - <p>In the case above, the stack trace shows that the function called - last was <c>erl_eval:eval_op/3</c>. See <em>Erlang Reference - Manual, Errors and Error handling</em>, for more information - about stack trace.</p> - - <p>Debugger emulates the stack trace by keeping track of recently +{'EXIT',{badarith,[{erlang,'+',[a,1],[]}, + {erl_eval,do_apply,5,[{file,"erl_eval.erl"},{line,562}]}, + {erl_eval,expr,5,[{file,"erl_eval.erl"},{line,359}]}, + {shell,exprs,7,[{file,"shell.erl"},{line,668}]}, + {shell,eval_exprs,7,[{file,"shell.erl"},{line,623}]}, + {shell,eval_loop,3,[{file,"shell.erl"},{line,608}]}]}}</pre> + + <p>See the <em>Erlang Reference Manual, Errors and Error handling</em>, + for more information about the stack trace.</p> + + <p>The Debugger emulates the stack trace by keeping track of recently called interpreted functions. (The real stack trace cannot be used, as it shows which functions of the Debugger have been called, rather than which interpreted functions).</p> |