Insert fmt.Printf() calls into your code. If you aren't familiar with how to get timestamped, filename:line-number prints to create a log of your run, I demonstrate that here: https://github.com/glycerine/vprint
In my experience, prints are how 99% of debugging should be done. If you don't have a console (stdout), write them to a file instead. On linux, the gdb debugger can give you alot of information. On windows, visual studio's debugger will do the same. However debuggers are very slow to use compared to generating and analyzing a log file. The only real thing that the debugger can do that logging cannot is to set watchpoints on memory locations (using special purpose CPU facilities), and then to stop the program when that address is written. On linux, strace is also quite helpful. On Friday, September 30, 2022 at 12:58:18 AM UTC-5 squadglad...@gmail.com wrote: > Hi everyone, > > Is there any way to debug DLL files once it is loaded? > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1bc04df4-0ebe-4692-bf98-ae4da7e15604n%40googlegroups.com.
