These are chat archives for derekparker/delve

8th
Mar 2016
Evan Digby
@evandigby
Mar 08 2016 18:59
@aarzilli I am still not able to reproduce in a smaller / toy test case. I wonder if it has to do with the size/footprint of the binary. It's a fairly large project.
Alessandro Arzilli
@aarzilli
Mar 08 2016 19:05
very likely
I'll try something to fix it later this week
it's likely the same problem as the other issue
Evan Digby
@evandigby
Mar 08 2016 19:07
Wherever it stores the map type structs is definitely being corrupted somehow... I'll be curious to know how (I don't know much about the internals of a Go binary)
Fortunately it works in Linux so I've been debugging in Vagrant for now... but getting debugging working in VS Code (IDE integration) would be a huge bonus. (To be clear, the tests I ran for you were NOT run in code--I wanted to rule out the integration being the culprit)
Alessandro Arzilli
@aarzilli
Mar 08 2016 19:09
if you look at the disassembly I made you do, it says exactly where the type information is
it's nothing special
I think the problem is that OS X API for debugging are racy, I've looked at lldb code and they have a sleep call before calling execve...
we try to do a synchronization using a pipe but maybe it's just not possible