-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proctl_test.go:23: Launch(): could not fork/exec #134
Comments
You have to provide an environment variable I will update the makefile to give a more meaningful error if that env var isn't there, however have you taken the steps to create a self signed cert? The steps are outlined in the README. |
Yes I did that - you can see in the shell output On Wed, May 20, 2015 at 2:10 AM, Derek Parker notifications@github.com
|
Ah, should have looked a little closer! Sorry about that. A few questions:
Thanks, I really appreciate that! |
Hi, no those test cases for the proctl package are failing, with or without the cert - same errors. But I could run go test on all the other packages. Note, when run as root, I did some printf-ing to get more info from the C code, which led me towards the Cheers |
My delve version: |
@laher sorry for the delay in getting back to you. So, to clarify, were you able to use that same cert to successfully run the tests previously? If that cert never worked before, it could just be an issue with the CERT that was created. |
No I haven't been able to run the tests with the cert, so you're probably right. I'll try re-creating a cert and do some more diagnostics on it if I run into problems. I'll let you know once I get a chance to look into it. Ta |
Sounds good, if you happen to fix the issue by regenerating a cert just close this issue out. |
I need to +1 here and say I have the same problem. Followed the guide and the cert exists in my system keychain.
|
Worth adding the signing is present on my main dlv command similar issue with 'debugger isn't running'
|
Last week I tried some new certs and got no further. But today I just So, here it is on a basic "Hello world!" app:
When I run various other commands, I get the following:
... |
@laher are you able to run the tests now? Can you point me to the source code of the program you're trying to debug in the last example? |
Yes, I can run the tests now. BUT, only if I Here's my 'Hello world' (I previously tried more substantial programs - same result):
|
@laher definitely make a ticket about that |
Hey! You fixed that path issue. I was just making a pull request, and then I realised it was already fixed. Sweet as. |
I had the same issue, until I killed taskgated as per the instructions: $ ps -ax | grep taskgated
$ sudo kill 107 #the process ID that printed for me from the above grep I then re-ran the tests, and re-built Delve, everything proceeded fine from this point forward. |
Going to close this issue as it should be solved. Please reopen if not. |
I cannot reopen, I think, as I am not the original submitter, but I am having the same issue as well. Tried the above steps in various combinations (killing taskgated, created several certificates, etc): still the "could not fork/exec" issue persists. |
How should I do? |
I should note that delve now works for me on my mac, since about 2 months On Wed, Feb 24, 2016 at 2:03 AM, Orson Wang notifications@github.com
|
That's good. it's only the record of I trying to figure out how to making it work on my OSX 10.11.4 Beta and golang 1.6. |
Only Note: Also it's not clear how you can test the certificate.
Assuming if this works without sudo, all certificate steps are done correctly and it's not the certificate or the permissions of the certificate or the taskgated state?
|
@gertcuykens: try installing with homebrew (either the permissions on the certificate are wrong or taskgated wasn't restarted): https://github.com/go-delve/homebrew-delve |
I will try that and it probably will work but aside from that in my above question, what is the reason I can use the same certificate in the same state as dlv was signed in and make a hello world app run without sudo? There must be yet another permission setting not mentioned in this thread. For me it's important that we understand all aspects of this, not just homebrew magic :) So basicly I want a test case other then dlv itself that gives me the exact same error message |
There is no other setting, you either missed one step or did not restart taskgated. Your helloworld example does not test the certificate because it doesn't do anything that requires a certificate. |
Ok make sense thank you, can you maybe add a few lines to the hello world example that would use the certificate and generate the same error? I really want to understand what is going on, and from there figure out if we could make better error messages. Just need the basics then I can direct my questions to stackoverflow to dissect more into this. |
@gertcuykens: if you |
Both certificates seem to be working now, indicating the restart taskgated was not successful the first time but still I am convinced it was restarted the first time for sure. So the question now would be can you make the brew certificate only Trust Code Signing?
|
* [#175987096] Added a log on sending webhooks with the relevant event * [#175987096] Log message for webhooks with status, event and destination
Running
make test
on a mac, I get the above error.Subsequently, when I try
make install
, it installs without complaint, but whendlv run
, it doesn't allow any subcommands (Command failed: debugger isn't running
)See output from
make test
, below (note that I sprintf'd the return value of C.fork_exec incase it helps. It returns '-1').Please let me know if you need any more info. Ta.
➜ delve git:(master) ✗ sw_vers -productVersion
10.10.2
➜ delve git:(master) ✗ CERT=dlv-cert make test
go test github.com/derekparker/delve/terminal github.com/derekparker/delve/dwarf/frame github.com/derekparker/delve/dwarf/op github.com/derekparker/delve/dwarf/util github.com/derekparker/delve/source github.com/derekparker/delve/dwarf/line
ok github.com/derekparker/delve/terminal 0.028s
ok github.com/derekparker/delve/dwarf/frame 0.006s
ok github.com/derekparker/delve/dwarf/op 0.005s
ok github.com/derekparker/delve/dwarf/util 0.006s
ok github.com/derekparker/delve/source 0.007s
ok github.com/derekparker/delve/dwarf/line 0.173s
cd proctl && go test -c github.com/derekparker/delve/proctl && codesign -s dlv-cert ./proctl.test && ./proctl.test && rm ./proctl.test
--- FAIL: TestExit (0.15s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestHalt (0.16s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestStep (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestBreakPoint (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestBreakPointInSeperateGoRoutine (0.16s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestBreakPointWithNonExistantFunction (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestClearBreakPoint (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestNextGeneral (0.16s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestNextGoroutine (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestNextFunctionReturn (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestNextFunctionReturnDefer (0.16s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestRuntimeBreakpoint (0.16s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestFindReturnAddress (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestSwitchThread (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestFunctionCall (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestVariableEvaluation (0.17s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestVariableFunctionScoping (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
--- FAIL: TestLocalVariables (0.00s)
proctl_test.go:23: Launch(): could not fork/exec -1
FAIL
make: *** [test] Error 1
The text was updated successfully, but these errors were encountered: