Skip to content

Unexpected signal during runtime execution #62

@thekid

Description

@thekid

This happens when running tests:

fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x1f146af00 pc=0x7f42d0fc7207]

runtime stack:
runtime.throw(0x75b263, 0x2a)
        /usr/lib/go-1.10/src/runtime/panic.go:616 +0x81
runtime.sigpanic()
        /usr/lib/go-1.10/src/runtime/signal_unix.go:372 +0x28e

goroutine 22 [syscall]:
runtime.cgocall(0x69f870, 0xc420035f20, 0x27)
        /usr/lib/go-1.10/src/runtime/cgocall.go:128 +0x64 fp=0xc420035ee0 sp=0xc420035ea8 pc=0x405a24
github.com/deuill/go-php._C2func_engine_init(0x0, 0x0, 0x0)
        _cgo_gotypes.go:420 +0x56 fp=0xc420035f20 sp=0xc420035ee0 pc=0x692656
github.com/deuill/go-php.New(0x5bb35b12, 0x9c3a8e4, 0x5f511f9)
        /mnt/c/Tools/cygwin/home/friebe/devel/go/src/github.com/deuill/go-php/engine.go:44 +0x36 fp=0xc420035f80 sp=0xc420035f20 pc=0x694ab6
github.com/deuill/go-php.TestValueStart(0xc4200131d0)
        /mnt/c/Tools/cygwin/home/friebe/devel/go/src/github.com/deuill/go-php/value_test.go:13 +0x22 fp=0xc420035fa8 sp=0xc420035f80 pc=0x6905a2
testing.tRunner(0xc4200131d0, 0x764430)
        /usr/lib/go-1.10/src/testing/testing.go:777 +0xd0 fp=0xc420035fd0 sp=0xc420035fa8 pc=0x4e0a40
runtime.goexit()
        /usr/lib/go-1.10/src/runtime/asm_amd64.s:2361 +0x1 fp=0xc420035fd8 sp=0xc420035fd0 pc=0x45d861
created by testing.(*T).Run
        /usr/lib/go-1.10/src/testing/testing.go:824 +0x2e0

goroutine 1 [chan receive]:
testing.(*T).Run(0xc4200131d0, 0x750f3d, 0xe, 0x764430, 0x47b901)
        /usr/lib/go-1.10/src/testing/testing.go:825 +0x301
testing.runTests.func1(0xc4200121e0)
        /usr/lib/go-1.10/src/testing/testing.go:1063 +0x64
testing.tRunner(0xc4200121e0, 0xc420059df8)
        /usr/lib/go-1.10/src/testing/testing.go:777 +0xd0
testing.runTests(0xc4201002e0, 0xae2c80, 0x1d, 0x1d, 0x4143c9)
        /usr/lib/go-1.10/src/testing/testing.go:1061 +0x2c4
testing.(*M).Run(0xc420116000, 0x0)
        /usr/lib/go-1.10/src/testing/testing.go:978 +0x171
main.main()
        _testmain.go:98 +0x151
FAIL    github.com/deuill/go-php        0.146s

Some research shows that is has to do with accessing receivers after a context is destroyed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions