These are chat archives for derekparker/delve

19th
Aug 2015
Florin Pățan
@dlsniper
Aug 19 2015 22:46
Hi, quick question: A few months ago delve could launch an existing binary but now it seems that the capability has been removed. Is there a good reason for this? I know you can theoretically start the binary then attach to its process so should this be the method that one uses? Thanks. It could also be that I'm blind and I can't see the option :D
Derek Parker
@derekparker
Aug 19 2015 22:49
@dlsniper that feature was actually only accidentally removed when the internal subcommand code got rewritten from a hand rolled solution to spf13/cobra. The issue is, last time I looked into it, supplying the root command with arguments was tricky. I think the solution may be to add a new subcommand for debugging existing binaries.
The preferred approach, however, is to use dlv debug so that it builds your program with the correct flags best suited for debugging.
Florin Pățan
@dlsniper
Aug 19 2015 22:55
I see, it makes sense. I asked because that when I'm launching the debugger from a controlled environment (like IntelliJ), I can have control on how the binary is compiled and the right flags are in place and so on. But there's no need for something in delve yet.
Thanks for the fast reply on the other issue ;)
Derek Parker
@derekparker
Aug 19 2015 23:03
@dlsniper check out derekparker/delve@7184535 :)
My train commute can be very productive, hah.
Florin Pățan
@dlsniper
Aug 19 2015 23:04
awesome, thank you!
haha :D