英文:
stays on same breakpoint when liteide step over pressed many times
问题
当我在LiteIDE中设置断点时，当断点被触发时，无论我按多少次"step over"，代码都会停留在同一个断点上。在异步记录中，我发现当我多次按"step over"时，"Stopped->core number"会发生变化。所以为什么Go语言会多次停留在同一个断点上，而在LiteIDE的异步记录中，"core"代表什么意思？
谢谢。
英文:
When I set a breakpoint in LiteIDE. When the breakpoint is hit. However, the code will stayed on the same breakpoint when I pressed step over many times. In the aync record, I found the Stopped->core number is changed when I pressed step over many times. So why Go stay on the same breakpoint many times and what is the "core" represented in async record of liteide?
Thanks
答案1
得分: 1
你可以查看这个教程，以确定是否正确配置了LiteIDE和gdb，以启用Go调试会话。
要确保(GDB基于)逐步调试器正常工作，需要执行以下操作：
Build -> Build Configuration... -> Custom -> BUILDARGS-> 输入：-gcflags "-N -l"- 通过执行以下调试运行来验证一切是否正常：
File -> Open Folder -> 点击：hello -> 选择- 在“Folders”窗格中双击“
for.go” Build -> Build(Ctrl-B)- 将光标放在第19行
- F9 (切换断点)
- F5 (开始调试)
- F5 (直到绿色箭头在第19行)
- 调试窗格应显示带有“i=4”和“j=7”的“Variables”选项卡。
“core”通常指的是核心转储，因此请检查您的程序在此处是否崩溃并生成核心转储。
英文:
You can check this tutorial in order to see if LiteIDE was properly configured with gdb in order to enable Go debugging session
> To make sure the (GDB based) step-by-step debugger works you need to do the following:
> Build -> Build Configuration... -> Custom -> BUILDARGS -> Enter: -gcflags "-N -l"
> Verify everything is working correctly by executing the following debug run:
> - File -> Open Folder -> Click: hello -> Choose
- Double click "
for.go" in the "Folders" pane Build -> Build(Ctrl-B)- Put cursor on line 19
- F9 (toggle breakpoint)
- F5 (start debugging)
- F5 (until green arrow is on line 19)
- Debug pane should show "Variables" tab with "i=4" and "j=7"
"core" generally refers to a core dump, so check if your program doesn't crash at this point, generating a core dump.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论