Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stacktraces doc: fix typos #36658

Merged
merged 1 commit into from
Jul 24, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 5 additions & 7 deletions doc/src/manual/stacktraces.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,18 +88,16 @@ Symbol("~/julia/usr/share/julia/stdlib/v0.7/REPL/src/REPL.jl")
julia> frame.line
5

julia> top_frame.linfo
julia> frame.linfo
MethodInstance for eval(::Module, ::Expr)

julia> top_frame.inlined
julia> frame.inlined
false

julia> top_frame.from_c
julia> frame.from_c
false
```

```julia-repl
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The block below was separated out in the past because it was the only one which wouldn't be doctested, but this difference doesn't exist anymore.

julia> top_frame.pointer
julia> frame.pointer
0x00007f92d6293171
```

Expand Down Expand Up @@ -130,7 +128,7 @@ julia> example()
[...]
```

You may notice that in the example above the first stack frame points points at line 4, where
You may notice that in the example above the first stack frame points at line 4, where
[`stacktrace`](@ref) is called, rather than line 2, where *bad_function* is called, and `bad_function`'s
frame is missing entirely. This is understandable, given that [`stacktrace`](@ref) is called
from the context of the *catch*. While in this example it's fairly easy to find the actual source
Expand Down