Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix uprobe target resolution #2180

Merged
merged 1 commit into from
Apr 5, 2022

Conversation

viktormalik
Copy link
Contributor

@viktormalik viktormalik commented Apr 1, 2022

Fixes #2065 as suggested in this comment by @fbs.

Checklist
  • Language changes are updated in man/adoc/bpftrace.adoc and if needed in docs/reference_guide.md
  • User-visible and non-trivial changes updated in CHANGELOG.md
  • The new behaviour is covered by tests

@viktormalik viktormalik force-pushed the uprobe-parser-fix branch 2 times, most recently from 8d58f81 to b4c43ba Compare April 1, 2022 12:42
If both a PID and a path is specified for uprobe, symbols from
/proc/PID/exe are used.
On the other hand, if a shortname for a library is used (e.g. u:libc:*),
then symbols from the library are used.

This unifies the behaviour by:
- using /proc/PID/exe only if no path is specified
- otherwise the path (or library) that the user specified is used.

See bpftrace#2065 for details.
@viktormalik viktormalik merged commit 625a304 into bpftrace:master Apr 5, 2022
@viktormalik viktormalik deleted the uprobe-parser-fix branch May 3, 2022 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"No probes to attach" with uretprobe in a shared library
2 participants