uprobe_apply(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… uprobe_apply(9) β€” like, the Kernel API Manual, section 9, bestie ✨

okay so picture this: you're deep in the Kernel API Manual (section 9, yes that one) and you find uprobe_apply. She's a little function, she's got main character energy, and she's here to add or remove breakpoints according to @uc->filter. Obsessed πŸ’–


✨ NAME ✨

uprobe_apply β€” add or remove the breakpoints according to @uc->filter 🎯


πŸ¦‹ SYNOPSIS πŸ¦‹

int uprobe_apply (struct uprobe *uprobe , struct uprobe_consumer *uc ,
       bool add );

like, that's her. that's the whole vibe ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • uprobe β€” the uprobe which "owns" the breakpoint πŸ‘‘ she's the one holding the keys, no cap.
  • uc β€” the consumer which wants to add more or remove some breakpoints 🫢 this is the one making requests.
  • add β€” literally just add or remove the breakpoints πŸ’… she does what she says on the tin.

🌸 RETURN 🌸

0 on success or a negative error code 😭 (so if it's negative, something did not slay).


🌈 SEE ALSO 🌈

all of them, together, a whole friend group of kernel functions 🫢 go read them, iykyk ✨


fr fr bestie, that's everything β€” every argument, every return value, no skips, no cuts πŸ’€ the facts stay iconic, periodt πŸ”₯

and that's a wrap 🎬 brought to you by ./kernel/events, dated October 2026 β€” mwah, see u in the next manpage, love u, bye πŸ’œπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from