[go-nuts] Re: All goroutines are parked during bgsweep() running. Is it a issue?

Hi, Please using `xz -d bgsweep.trace.xz ` decompress this file before running `go tool trace bgsweep.trace`. 在 2019年8月16日星期五 UTC+8下午5:19:03，gerald...@gmail.com写道： > > How about uploading the svg, so people

[go-nuts] All goroutines are parked during bgsweep() running. Is it a issue?

Hi All I found my application has a strange issue by go trace. All goroutines are parked during bgsweep() running. Is it a issue? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from i

[go-nuts] Re: Does runtime.RaceDisable not work in non-std library ?

According to https://github.com/golang/go/blob/7a6ccece877232fc58872c85fdf0718629b83d91/src/cmd/compile/internal/gc/racewalk.go#L45-L47 , the compile does not insert data race detecting code in package "sync". 在 2018年8月22日星期三 UTC+8下午6:25:24，nea...@gmail.com写道： > > Hi, > > When I copy the sync.

Re: [go-nuts] Does runtime.RaceDisable not work in non-std library ?

Thanks a lot. 在 2018年8月25日星期六 UTC+8上午1:32:12，Ian Lance Taylor写道： > > On Fri, Aug 24, 2018 at 12:28 AM, > > wrote: > > > >> go test -v -race -count=5 . > > === RUN TestSyncAPI > > == > > WARNING: DATA RACE > > Read at 0x00c4200ca080 by goroutine 8: > > _/Users/yanqing11

Re: [go-nuts] Does runtime.RaceDisable not work in non-std library ?

Hi Dave, 1. the report: > go version go version go1.10 darwin/amd64 > go test -v -race -count=5 . === RUN TestSyncAPI == WARNING: DATA RACE Read at 0x00c4200ca080 by goroutine 8: _/Users/yanqing11/test/go/sync1.(*Pool).Put() /Users/yanqing11/test/go/sync1/pool.go:108 +0

Re: [go-nuts] Does runtime.RaceDisable not work in non-std library ?

Hi lan, The sync.Pool has memory accesses in per-p private storage. Why it not reports `DATA RACE`, but it reports when I copy those code outside stdlib? I'm confused about this, or there is something wrong in https://gist.github.com/lrita/efa8c4ae555b4b7cceee29b4ed819652 Thanks. 在 2018年8月24日星

Re: [go-nuts] Does runtime.RaceDisable not work in non-std library ?

Thanks for your attention. Here is the code : https://gist.github.com/lrita/efa8c4ae555b4b7cceee29b4ed819652 When I run `go test -v -race -count=10 .` `TestSyncAPI` reports DATA RACE, `TestSyncAPI2` not reports. 在 2018年8月22日星期三 UTC+8下午10:34:35，Ian Lance Taylor写道： > > On Wed, Aug 22, 2018 at 3:

[go-nuts] Does runtime.RaceDisable not work in non-std library ?

Hi, When I copy the sync.Pool's source code in a repo, and using `//go:linkname` link those runtime functions manually. When I run `go test -race`, it reports `DATA RACE`. But the sync.Pool with the same test case does not report `DATA RACE`. Does runtime.RaceDisable not work in non-std library

[go-nuts] Re: Does sync.(*Pool).Put slow to cause latency spikes sometimes?

Yes, there is only pointers in sync.Pool. I think the sync.Pool only slow during GCing is a normal behavior. If the sync.Pool's method slow with out GCing is a runtime issue. I donot agree: sync.Pool just amortizes the cost of creating garbage The sync.Pool is reusing object and reducing crea

Re: [go-nuts] Does golang support SystemTap well?

Thanks your reply. You say "Systemtap uses the literal Go symbol names as C identifiers". But SystemTap 2.8 release say it support golang. It does do any adapting work for golang application? I cannot find more information for this. Do you know any up to date information for this? 在 2017年9月19日星期

Re: [go-nuts] Does golang support SystemTap well?

Thanks your reply. As I known, `pprof` only can tell your which function is busy on cpu, memory allocated/in-use and so on. But It cannot tell you a function latency/elapsed, how long we wait on a mutex. Is there any plan to add more feature in pprof ? 在 2017年9月19日星期二 UTC+8下午9:27:31，Ian Lance T

[go-nuts] Does golang support SystemTap well?

ENV : SystemTap version : 3.1/0.160 Linux kernal : 3.10.0-229.el7.x86_64 Golang : 1.8.3 Recently, I use SystemTap to do some tracing for a golang application. But it occurred many fatal error, e.g: SIGILL: illegal instruction PC=0x7fffe015 m=41 sigcode=2 ... SIGTRAP: trace t