weaver

weaver copied to clipboard

Add support for inspecting interface parameters on the stack

2

grantseltzer

dwarf.TagCompileUnit dwarf.TagSubprogram dwarf.TagVariable dwarf.TagTag(0) dwarf.TagFormalParameter dwarf.TagLexDwarfBlock dwarf.TagInlinedSubroutine dwarf.TagConstant dwarf.TagUnspecifiedType dwarf.TagPointerType dwarf.TagBaseType dwarf.TagStructType dwarf.TagMember dwarf.TagTypedef dwarf.TagSubroutineType dwarf.TagArrayType dwarf.TagSubrangeType

grantseltzer

Go 1.17 will support register based arguments instead of the stack (feature flagged)

1

Will certainly still be retrievable but will need to be feature flagged. I believe the go version string is passed into the binary debug information too so could auto-detect. https://github.com/golang/go/issues/40724

grantseltzer

At first can just print the addr of it, but later can add logic for printing out the contents of the map

grantseltzer

Sequence numbering/ordering for function calls

1

Currently there's no order for function calls, just whenever they come out of the kernel. It'd be useful to associate invocations in a map and order them.

grantseltzer

In this blog post Brendan Gregg has some examples of using a utility for installing probes on userspace probes: http://www.brendangregg.com/blog/2015-06-28/linux-ftrace-uprobe.html Being able to put a one line probe in would...

grantseltzer

The smoke-test breaks pretty easily. We should have go tests that actually execute weaver and do typed assertions for checking output. This'll make it really easy to port to new...

grantseltzer

Weaver is built for x86_64 linux platforms. It would be great in the future to support ARM, but for now it'd make sense to use [build constraints](https://golang.org/pkg/go/build/#hdr-Build_Constraints)

grantseltzer

grantseltzer

Add the ability to let users specify method receiver to be traced

2

grantseltzer