Thanks Dave!
> On Dec 5, 2017, at 7:57 PM, Dave Cheney wrote:
>
> The pprof packages are maintained elsewhere,
> https://github.com/google/pprof, we fork off a copy each major
> release.
>
> On Wed, Dec 6, 2017 at 11:45 AM, Robert Frangioso
> wrote:
>>
>> I’ve noticed there appear to be chan
The pprof packages are maintained elsewhere,
https://github.com/google/pprof, we fork off a copy each major
release.
On Wed, Dec 6, 2017 at 11:45 AM, Robert Frangioso
wrote:
>
> I’ve noticed there appear to be changes with 1.9.2 from prior versions that
> I have used. Still playing with it but ha
I’ve noticed there appear to be changes with 1.9.2 from prior versions that I
have used. Still playing with it but has there been a redesign of the profiling
package I didn’t notice?
> On Dec 5, 2017, at 4:51 PM, Dave Cheney wrote:
>
> Can you please check if this is happening with the curre
A couple of questions on understanding go pprof's memory profile...
When I list a certain function (with --alloc_objects), I see an allocation
number associated with an import line mysteriously. I am pretty certain I
can rule out any source line offset. For example,
(pprof) list foo
Total: 5348
