-
Notifications
You must be signed in to change notification settings - Fork 374
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
Fail to init with delve #154
Comments
Have no idea. I don't have and don't use macosx. To debug it obviously you need to understand how termbox works and what it does. Source code is there. It's not a big lib. |
Also is delve a Go debugger? Don't use it as well. But maybe it it works under linux I'll take a look at the weekend. |
A workaround is to run the termbox-go application, and then attach with delve from another terminal.
This allows delve to manipulate the terminal in its own terms, while termbox-go manipulates the other terminal in its own. It's a bit more tedious, especially since you need to find the PID of the app you're debugging, and you might want to block the app's execution until after you've attached, probably using a signal. But using the |
as soon as I attach with delve input no longer works in the application - the application continues to run though. makes it impossible to control the application in order to reach a desired breakpoint. any work arounds for this? |
System
With delve, termbox.Init() fail with "SYS_IOCTL: interrupted system call" err.
What should I do for debugging with delve?
The text was updated successfully, but these errors were encountered: