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 Taylor写道： > > On Tue, Sep 19, 2017 at 1:50 AM, <nea...@gmail.com <javascript:>> wrote: > > 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=0x7fffffffe015 m=41 sigcode=2 > > > > ... > > > > SIGTRAP: trace trap > > PC=0x7fffffffe001 m=45 sigcode=0 > > > > .... > > > > > > fatal error: unknown caller pc > > .... > > > > Is the PC corrupted by SystemTap? > > Or SystemTap make some conflict with go runtime? > > The SystemTap 2.8 release say it support golang. Is it right? > > https://sourceware.org/ml/systemtap/2015-q2/msg00160.html > > > > I search some topic related to this here, but those topics is > obsoleted.Is > > there any newly update? > > In Go 1.9 the Go compiler uses frame pointers by default. That should > at least give you better tracebacks. > > I don't know where those signals are coming from, though. I don't > know why Go programs would not work with systemtap. > > Ian > -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
