- Sort Score
- Result 10 results
- Languages All
Results 1 - 5 of 5 for forkExec (0.14 sec)
-
src/syscall/exec_unix.go
} // Combination of fork and exec, careful to be thread safe. func ForkExec(argv0 string, argv []string, attr *ProcAttr) (pid int, err error) { return forkExec(argv0, argv, attr) } // StartProcess wraps [ForkExec] for package os. func StartProcess(argv0 string, argv []string, attr *ProcAttr) (pid int, handle uintptr, err error) { pid, err = forkExec(argv0, argv, attr) return pid, 0, err }
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Feb 26 21:03:59 UTC 2024 - 8.7K bytes - Viewed (0) -
src/cmd/cgo/internal/testplugin/testdata/forkexec/main.go
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri May 12 11:59:56 UTC 2023 - 502 bytes - Viewed (0) -
src/syscall/exec_unix_test.go
} func TestForkExecNilArgv(t *testing.T) { defer func() { if p := recover(); p != nil { t.Fatal("forkExec panicked") } }() // We don't really care what the result of forkExec is, just that it doesn't // panic, so we choose something we know won't actually spawn a process (probably). syscall.ForkExec("/dev/null", nil, nil)
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Mar 22 04:41:27 UTC 2024 - 7.9K bytes - Viewed (0) -
src/cmd/vendor/golang.org/x/sys/plan9/mkall.sh
# func RawSyscall(trap, a1, a2, a3 uintptr) (r1, r2, err uintptr); # # The first and second are the standard ones; they differ only in # how many arguments can be passed to the kernel. # The third is for low-level use by the ForkExec wrapper; # unlike the first two, it does not call into the scheduler to # let it know that a system call is running. # # * syscall_${GOOS}.go # # This hand-written Go file implements system calls that need
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Mar 15 19:02:39 UTC 2021 - 4.4K bytes - Viewed (0) -
src/cmd/vendor/golang.org/x/sys/unix/README.md
func RawSyscall(trap, a1, a2, a3 uintptr) (r1, r2, err uintptr) ``` The first and second are the standard ones; they differ only in how many arguments can be passed to the kernel. The third is for low-level use by the ForkExec wrapper. Unlike the first two, it does not call into the scheduler to let it know that a system call is running. When porting Go to a new architecture/OS, this file must be implemented for each GOOS/GOARCH pair.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Dec 06 14:32:58 UTC 2021 - 8.5K bytes - Viewed (0)