On Wed, Feb 22, 2023 at 6:43 PM Xiangdong Ji wrote:
>
> Looks like the print* helper functions may run into deadlocks if the printer
> Goroutine is rescheduled to a different M to execute 'printunlock' as the "if
> mp.printlock==0" checking is likely to fail if M has changed.
Have you seen this
On Thu, Feb 23, 2023 at 1:18 PM David Choi (jsoneaday)
wrote:
>
> Hi I'm trying to build my project as C so I can call it from Nodejs. But when
> I run the command "go build -buildmode=c-shared -o keyring.so ." I get a so
> file but no h C header.
>
> I am running this on Mac M1. I read somethin
Hi I'm trying to build my project as C so I can call it from Nodejs. But
when I run the command "go build -buildmode=c-shared -o keyring.so ." I get
a so file but no h C header.
I am running this on Mac M1. I read something about cgo being disabled by
default on mac's without the c toolchain bu
Thank you for the clarification.
On Thu, Feb 23, 2023 at 6:30 PM Ian Lance Taylor wrote:
> On Thu, Feb 23, 2023 at 9:02 AM 'Arsene Gandote' via golang-nuts
> wrote:
> >
> > I would like to report a memory leak in golog (
> https://github.com/golang/glog). It seems the repo does not have any
> i
On Thu, Feb 23, 2023 at 9:02 AM 'Arsene Gandote' via golang-nuts
wrote:
>
> I would like to report a memory leak in golog
> (https://github.com/golang/glog). It seems the repo does not have any issues
> links.
>
> This is the stack trace:
>
> found unexpected goroutines:
> [Goroutine
I've got a program I maintain that uses a 3rd party module. That module has
a bug in it, and I've raised a pull request to fix it.
But... I need to release a new version of my program as soon as possible.
My understanding was that I can use a replace directive in the go.mod file
to replace the
thanks
21 Şubat 2023 Salı tarihinde saat 07:49:29 UTC+2 itibarıyla Ian Lance
Taylor şunları yazdı:
> On Mon, Feb 20, 2023 at 10:50 AM 彭锟（ainman）
> wrote:
> >
> > for example, I have file "pkg/A/internal/A.go" that has code like shown
> below
> >
> > ```golang
> >
> > package internal
> >
Using location from stamp 2023-02-09 10:55:00 +0100 CET is unix 1675936500
(true) 2023-02-09 02:55:00 -0700 MST is unix 1675936500 (true) Using
time.Parse 2023-02-09 10:55:00 + CET is unix 1675940100 (false)
2023-02-09 02:55:00 + MST is unix 1675911300 (false) As reference
2023-02-09 0
Hello Team,
I would like to report a memory leak in golog (
https://github.com/golang/glog). It seems the repo does not have any issues
links.
This is the stack trace:
found unexpected goroutines:
[Goroutine 6 in state chan receive, with
github.com/golang/glog.(*loggingT).flushDaemon
