Investigate addresses from /proc/<pid>/maps::[uprobes] in stack traces.

[etep]

Describe the Task We noticed addresses from [uprobes], a memory region shown in /proc/<pid>/maps in some stack traces. We have determined that the go uprobe for casgstatus is responsible for this stack trace, but we do not know why we see this address in stack traces, nor do we know if there is some additional perf impact for this probe.

Subtasks

• [ ] Investigate why addresses from this memory region are in stack traces.
• [ ] Try to understand if some particular part of our casgstatus probe is responsible (i.e. because other uprobes do not appear in stack traces).
• [ ] Evaluate perf of go apps with and without our uprobes.
• [ ] Try to reproduce this kind of a stack trace with a targeted/hand-crafted uprobe (either in go, or C/C++).
• [ ] Also, investigate why [heap] can appear in stack traces. Produce a hand-crafted/targeted app showing [heap] in stack traces.