On Tue, Sep 19, 2017 at 1:50 AM, <neal...@gmail.com> 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.
