> I don't know why Go programs would not work with systemtap. Because when tracing function call returns systemtap installs trampolines in the return address slots. This confuses traceback, which doesn't expect systemtap functions in the stack trace. It also breaks stack frame copy for the same reason.
I don't know why the original SIGILL comes from exactly, but I have experienced it also, among many other problems. Systemtap doesn't work well with Go. In fact, a few years back it didn't work at all. Systemtap uses the literal Go symbol names as C identifiers in the generated C kernel driver (whtout mangling), which then didn't even compile. -- Aram Hăvărneanu -- 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.
