Nice, stress.bash is indeed super simple, but finds issues that -race alone
does not. Thanks for that.
I'm still having the 100% cpu peg problem. I was able to observe it under
go1.7.4 as well, so it's not specifically a go1.8rc3 issue.
If anyone can supply information on the mystery runtime._ExternalCode that
would be super helpful.
I'm not linking in any cgo libraries. (beyond what the runtime does
automatically for dns). Err... so actually there are some C libs... what is
the magic phrase for not linking any C .so?
[jaten@biggie bin]$ ldd vhaline
linux-vdso.so.1 => (0x00007ffecfd3c000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f2a6b5dc000)
libc.so.6 => /lib64/libc.so.6 (0x00007f2a6b21b000)
/lib64/ld-linux-x86-64.so.2 (0x00007f2a6b808000)
[jaten@biggie bin]$
On Tue, Feb 7, 2017 at 12:31 AM, Dave Cheney <[email protected]> wrote:
> https://dave.cheney.net/2013/06/19/stress-test-your-go-packages
>
> It's just a tiny script to randomly set GOMAXPROCS
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "golang-nuts" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/golang-nuts/uytOgKskQdg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
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 it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
