their support forums, sorry I don't have those details, i've
> never tried to get support for their product.
>
thanks Dave.
>
> On Wednesday, 4 April 2018 21:52:08 UTC+10, sothy shan wrote:
>>
>>
>>
>> On Tuesday, April 3, 2018 at 4:50:36 PM UTC+2, Dave Che
On Tuesday, April 3, 2018 at 4:50:36 PM UTC+2, Dave Cheney wrote:
>
> I’ve not seen that problem before. I’d hazard a guess that it’s an
> incorrect go installation. Don’t set goroot, basically ever. But it’s just
> a guess.
>
It is basically problem when I run in docker container. This is
On Saturday, March 31, 2018 at 12:15:34 AM UTC+2, Dave Cheney wrote:
>
> It looks like you’re stopping the block profile immediately after starting
> it.
>
> Try github.com/pkg/profile which will take care of the plumbing for you.
Thanks Dave for pointing your code.
After viewing your code,
Hello,
I want to use blocking profiler in my go application. I use go1.10. My
applcation is running as docker instance?.
I include the following code into my application.
f,err :=os.Create("/tmp/test_blocking.prof")
if err != nil {
Hello,
I am using go application as service in linux docker environment. My
application is given 1 cpu when defining docker-compose file.
I enabled to cpu profiler within my application. After running my testing,
I stop my container and using docker cp, I copied test.prof into local host.
