Hello,

I'm doing some research and I would like to know what kind of debugging 
information any go binary can be compiled with in the DWARF section. In 
particular, I need to know that the address of each individual instruction 
can be accounted for in the binary. 


Is there any way to know what the debugging information specifically should 
be contained in a go binary? Or to influence what the debugging information 
will contain? Or for that matter, to get the go compiler to play nice, and 
possibly give me the address of every single instruction for a given target 
as an additional output?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to