Hi there.
Any body here debugging goasm created executables with windbg ?
I,m exploring debuggers at the moment, but i think windbg needs the pdb file to function, goasm creates a dbg file.
after issuing a .reload /f command i get
*** ERROR: Module load completed but symbols could not be loaded for image00400000
So i,m guessing this means it does not see or can read goasm symbol file ?
Hi Dogim
It's the linker which produces the symbol information for the debugger.
Try using the GoLink command /debug coffThis will embed the debug information about symbol data in the exe and this should be readable by Windbg.
Alternatively you could use another linker +GoAsm which does produce a pdb file.
Quote from: jorgon on January 23, 2011, 09:21:43 PM
Hi Dogim
It's the linker which produces the symbol information for the debugger.
Try using the GoLink command /debug coffThis will embed the debug information about symbol data in the exe and this should be readable by Windbg.
Alternatively you could use another linker +GoAsm which does produce a pdb file.
Hi Jorgon,
That did the job,debug info are visible in the machine code mode.