Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

2019-05-13 Thread Jason E. Aten
andrey: voice your support on https://github.com/golang/go/issues/21881 It's been a known issue since 2017 and really needs to be fixed. On Tuesday, May 14, 2019 at 4:05:55 AM UTC+2, andrey mirtchovski wrote: > > file an issue, please, if you have not done so already. i'd like to follow > it.

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

2019-05-13 Thread Jason E. Aten
Further confirmation: with the env var GOROOT set to C:\Go, it is sufficient to have exactly one file under then entire C:\Go directory tree: C:\Go\lib\time\zoneinfo.zip alone allows the Go runtime to start cleanly inside the DLL. The zoneinfo.zip file allows the runtime to start. We should re

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

2019-05-13 Thread andrey mirtchovski
file an issue, please, if you have not done so already. i'd like to follow it. On Mon, May 13, 2019 at 8:01 PM Jason E. Aten wrote: > > Indeed, confirming data: I can re-create the crashing circumstances > immediately by renaming C:\Go to C:\Go1.12.5. > > On Tuesday, May 14, 2019 at 3:53:10 AM U

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

2019-05-13 Thread Jason E. Aten
Indeed, confirming data: I can re-create the crashing circumstances immediately by renaming C:\Go to C:\Go1.12.5. On Tuesday, May 14, 2019 at 3:53:10 AM UTC+2, Jason E. Aten wrote: > > Installing the Go build environment locally on the deploy host fixed the > crash. I'm guessing it is probably t

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

2019-05-13 Thread Jason E. Aten
Installing the Go build environment locally on the deploy host fixed the crash. I'm guessing it is probably the missing timezone data on Windows, as in https://github.com/golang/go/issues/21881 or some other assumption by the runtime inside the DLL that it is running on a machine that has the

Re: [go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

2019-05-10 Thread Ian Lance Taylor
On Fri, May 10, 2019 at 1:43 PM Jason E. Aten wrote: > > I wondering if anyone can shed some light on > > a) how I might understand when the Go runtime inside a DLL is supposed to be > initialized; In c-shared mode the function _rt0_amd64_windows_lib is supposed to be called when the DLL is init

[go-nuts] go runtime in DLL not getting intialized(?) on some windows hosts

2019-05-10 Thread Jason E. Aten
I'm stumped on why the Go runtime would not be initialized inside my c-shared DLL. I'm building a mixed Go and C DLL for windows, using go build -buildmode=c-shared On one instance of Windows 2016, everything runs fine, both with go1.12.5 and with go1.10.8. However, on an instance of Windows