Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for crash (0.13 sec)

  1. doc/next/6-stdlib/99-minor/runtime/debug/42888.md

    The [SetCrashOutput] function allows the user to specify an alternate
    file to which the runtime should write its fatal crash report.
    It may be used to construct an automated reporting mechanism for all
    unexpected crashes, not just those in goroutines that explicitly use
    Plain Text
    - Registered: Tue May 07 11:14:38 GMT 2024
    - Last Modified: Fri Apr 12 20:57:18 GMT 2024
    - 283 bytes
    - Viewed (0)
  2. src/cmd/cgo/internal/test/callstub_linux_ppc64le.go

    //	return notoc_func();
    // }
    import "C"
    import "testing"
    
    func testPPC64CallStubs(t *testing.T) {
    	// Verify the trampolines run on the testing machine. If they
    	// do not, or are missing, a crash is expected.
    	if C.TestPPC64Stubs() != 0 {
    		t.Skipf("This test requires binutils 2.35 or newer.")
    	}
    Go
    - Registered: Tue Apr 23 11:13:09 GMT 2024
    - Last Modified: Fri Sep 22 15:06:17 GMT 2023
    - 540 bytes
    - Viewed (0)
  3. misc/cgo/gmp/gmp.go

    	init bool
    }
    
    // NewInt returns a new Int initialized to x.
    func NewInt(x int64) *Int { return new(Int).SetInt64(x) }
    
    // Int promises that the zero value is a 0, but in gmp
    // the zero value is a crash.  To bridge the gap, the
    // init bool says whether this is a valid gmp value.
    // doinit initializes z.i if it needs it.  This is not inherent
    // to FFI, just a mismatch between Go's convention of
    Go
    - Registered: Tue Apr 30 11:13:12 GMT 2024
    - Last Modified: Mon Apr 11 16:34:30 GMT 2022
    - 9.5K bytes
    - Viewed (0)
Back to top