Please unzip the file and read the text file then view
the exception and code generated by GoBug.
If that instruction does not work, as part of the debugging process for an exception you would generally select the "do nothing at the moment" option. However, that is the command for the debugger, not you! :biggrin: You need to look at the value of eax which is supposed to point into memory, and if it is not a valid number, you need to trace back how it got its incorrect value. Before you do that though, you check to see if what you have coded is correct to start with, and in your case it isn't since you were trying to test the return value of GetMessage in eax, but instead you attempted to test some value in memory [eax]. Correction:
cmp eax,-1
Thank you WJR for responding.
That's kind of embarassing but not my 1st.....
Quote from: wjr on August 29, 2012, 09:27:52 AM
If that instruction does not work, as part of the debugging process for an exception you would generally select the "do nothing at the moment" option. However, that is the command for the debugger, not you! :biggrin:
so THAT'S where i have gone wrong all these years :lol:
you fixed me good, Wayne
Super, a qword of caution though - now you need to carefully watch your step... what you step over... what you step into...