Delve: proc: Fix Launch race condition on OSX

Created on 18 Mar 2016  Â·  7Comments  Â·  Source: go-delve/delve

The current implementation of fork/exec'ing the child process, and then trying to parse information out of the running process seems to be racy. It seems the child process is not fully initialized when we try and parse information from it.

We seem to get errors similar to:

could not launch process: Could not determine version number: could not read string len could not read memory

areproc kinbug kinregression prioritP0

Most helpful comment

Currently working on this issue as we speak. I have some OSX fixes and
general refactoring / code cleanup patches I'll be submitting soon.
On Tue, Apr 26, 2016 at 1:58 PM Nathan Corvino [email protected]
wrote:

Saw some work happen on this recently and just wanted to offer
encouragement. Would be great to see this issue resolved. Thanks!

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/derekparker/delve/issues/464#issuecomment-214883908

  • Derek

All 7 comments

I am working on a fix for this, I hope to have up soon.

Hi
I face some similar issue in mac
when start debug by dlv, it only work sometimes.

I trace syscall in dlv process, it will received the request like create 5 break point and then continue.
created breakpoint: created breakpoint: created breakpoint: created breakpoint: created breakpoint: continue

I turn on dlv's logger
when working properly, log will look like
created breakpoint: created breakpoint: created breakpoint: continue

but sometimes the same commands but the sequence will become
continue
and block all the other requests.

seems like the command's sequence is not always equal to execution sequence.
then intellij will halt there.

Saw some work happen on this recently and just wanted to offer encouragement. Would be great to see this issue resolved. Thanks!

Currently working on this issue as we speak. I have some OSX fixes and
general refactoring / code cleanup patches I'll be submitting soon.
On Tue, Apr 26, 2016 at 1:58 PM Nathan Corvino [email protected]
wrote:

Saw some work happen on this recently and just wanted to offer
encouragement. Would be great to see this issue resolved. Thanks!

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/derekparker/delve/issues/464#issuecomment-214883908

  • Derek

Hello, any progress on this issue?
I am experiencing the same problem with my IntelliJ IDE on my Mac (go development)
Even a workaround should be enough until it's fixed

Let me know if I can help with testing

Thanks for your work

hey, no progress on this one?

This should be fixed on master.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

luminacious picture luminacious  Â·  5Comments

devtoro picture devtoro  Â·  6Comments

saleemjaffer picture saleemjaffer  Â·  4Comments

runningbar picture runningbar  Â·  4Comments

ramya-rao-a picture ramya-rao-a  Â·  3Comments