FS#64410 - [go][go-pie] SIGSECV on `go run -race`
Attached to Project:
Community Packages
Opened by Mikhail Shiryaev (Felixoid) - Wednesday, 06 November 2019, 14:31 GMT
Last edited by Morten Linderud (Foxboron) - Wednesday, 13 May 2020, 19:40 GMT
Opened by Mikhail Shiryaev (Felixoid) - Wednesday, 06 November 2019, 14:31 GMT
Last edited by Morten Linderud (Foxboron) - Wednesday, 13 May 2020, 19:40 GMT
|
Details
Description: When `go run -race` is executed it causes panic
with the following trace:
``` go run -race test.go ==10054==ERROR: ThreadSanitizer failed to allocate 0x26b1000 (40570880) bytes at address 175af88584000 (errno: 12) unexpected fault address 0x0 fatal error: fault unexpected fault address 0x556be20bd1ae fatal error: fault unexpected fault address 0x556be2b09c2a fatal error: fault [signal SIGSEGV: segmentation violation code=0x2 addr=0x556be2b09c2a pc=0x556be2b09c2a] goroutine 1 [running, locked to thread]: runtime: unexpected return pc for runtime.throw called from 0x556be20bd080 stack: frame={sp:0x7ffc497465c0, fp:0x7ffc497465f0} stack=[0xc000036000,0xc000036800) runtime.throw(0x3, 0x3) /usr/lib/go/src/runtime/panic.go:774 +0x74 fp=0x7ffc497465f0 sp=0x7ffc497465c0 pc=0x556be205b694 exit status 2 ``` It's fine when I use the standard go package Additional info: * package version(s): community/go-pie 2:1.13.4-1 Steps to reproduce: * install go-pie * Create a file test.go with content ``` package main import "os" func main() { os.Exit(0) } ``` * run `go run -race test.go` |
This task depends upon
Closed by Morten Linderud (Foxboron)
Wednesday, 13 May 2020, 19:40 GMT
Reason for closing: No response
Wednesday, 13 May 2020, 19:40 GMT
Reason for closing: No response
Comment by
Morten Linderud (Foxboron) -
Saturday, 14 December 2019, 13:34 GMT
I believe this is expected behavior with pie?