https://github.com/iovisor/bcc/blob/master/docs/reference_gu... lists the hook points where BPF code can be attached. Also take a look at https://blogs.oracle.com/linux/notes-on-bpf-1 (there are follow-ups - https://blogs.oracle.com/linux/notes-on-bpf-7 has the links at the bottom) and from the Linux source, https://github.com/torvalds/linux/blob/master/include/uapi/l.... https://docs.cilium.io/en/latest/bpf/ is an extensive reference but with an emphasis on the network-related areas (xdp, tc).

related documentation in the Developer Guide: https://docs.aws.amazon.com/apigateway/latest/developerguide...

The current problem though is that it requires all your code + all the dependencies to be under $GOPATH/src. https://github.com/golang/go/issues/33655 starts with: "At this time, the godoc command is only able to display packages that are located in a GOPATH workspace."

Here's a deriv example in Go: https://play.golang.org/p/kUM5qn7oiXg

I find that it follows the functional spec quite closely, thanks to Go functions being first class citizens.

would not it be easier and cleaner to use the Android's REPO tool [1] to pin down the versions and layout your workspace? At least the REPO allows you to write down the dependency information in a declarative manner instead of Makefile scripting snippets.

[1] https://source.android.com/source/using-repo.html

Gave me a bigger jolt than the morning coffee - here's a spoiler in Go: http://play.golang.org/p/YBfxhjvsOB

Tainted mode for Javascript and tools for identifying DOM XSS (similar to DOMinator) would be really useful for security testing and audits of the modern complex sites. There is a bug open https://bugzilla.mozilla.org/show_bug.cgi?id=811877 - hopefully it can be given sufficiently high attention and priority!