0

I am following the instructions described in https://www.erlang.org/doc/apps/debugger/debugger_chapter to start the debugger. However, after debugger:start()., I only get the message Command is taking a long time, type Ctrl+G, then enter ‘i’ to interrupt, when according to the manual, the monitor window should open immediately.

After I press CTRL+C and then c, the debugger monitor window opens.

Why is that? I am attaching a video and 2 screenshots of the screen after debugger:start() was called.

Video: https://sendvid.com/nra91kna

Screenshot of the screen after debugger:start() was called. Screenshot of the screen after debugger:start() was called and CTRL+C and c keys pressed.

Thanks!

Improve this question
Related questions
628
"The breakpoint will not currently be hit. The source code is different from the original version." What does this mean?
93
React Native app stuck on blank white screen with remote debugging using Nuclide
3
Why can you create multiple monitor references to the same process in Erlang?
Load 6 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.