POSIX_TRACE_GET_FILTER(3P)

💖 POSIX_TRACE_GET_FILTER(3P) 💖

okay bestie, welcome to the POSIX Programmer's Manual — this one lives in section 3P and it's all about tracing. Pull up a chair, grab a boba, we're doing filters today 🧋✨

🚨 PROLOG 🚨

Real talk first, no cap: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ — so like, go consult the corresponding Linux manual page for the details of Linux behavior — or honestly? The interface may not be implemented on Linux at all. 💀 So vibe check your platform before you get attached.

---

✨ NAME ✨

posix_trace_get_filter, posix_trace_set_filter — retrieve and set the filter of an initialized trace stream (TRACING)

Like, one gets, one sets. Dynamic duo energy. 👑

---

🌸 SYNOPSIS 🌸

#include <trace.h>

int posix_trace_get_filter(trace_id_t trid, trace_event_set_t *set);
int posix_trace_set_filter(trace_id_t trid,
    const trace_event_set_t *set, int how);

---

💅 DESCRIPTION 💅

So posix_trace_get_filter() shall retrieve, into the argument pointed to by set, the actual trace event filter from the trace stream specified by trid. It's giving "show me what you're filtering right now bestie". 🔍

Then posix_trace_set_filter() shall change the set of filtered trace event types after a trace stream identified by the trid argument is created. And the way that it's flexible?? You may call this function prior to starting the trace stream, or while the trace stream is active. Both. Either. We love range. 🦋

By default, if no call is made to posix_trace_set_filter(), all trace events shall be recorded — that is, none of the trace event types are filtered out. Everything gets in, the door is open, no bouncer. 🎀

If this function is called while the trace is in progress, a special system trace event, POSIX_TRACE_FILTER, shall be recorded in the trace indicating both the old and the new sets of filtered trace event types (see Table 2-4, Trace and Trace Event Filter Options: System Trace Events and Table 2-6, Trace, Trace Log, and Trace Event Filter Options: System Trace Events). Receipts kept, always. 🧾

⚠️ If the posix_trace_set_filter() function is interrupted by a signal, an error shall be returned and the filter shall not be changed. In this case, the state of the trace stream shall not be changed. Like, nothing happened, the vibe is preserved, no half-changes. 🫶

The value of the argument how indicates the manner in which the set is to be changed and shall have one of the following values, as defined in the <trace.h> header:

• POSIX_TRACE_SET_EVENTSET — the resulting set of trace event types to be filtered shall be the trace event type set pointed to by the argument set. Straight swap, out with the old. 🔄
• POSIX_TRACE_ADD_EVENTSET — the resulting set of trace event types to be filtered shall be the union of the current set and the trace event type set pointed to by the argument set. Adding to the collection, we're accumulating. ➕
• POSIX_TRACE_SUB_EVENTSET — the resulting set of trace event types to be filtered shall be all trace event types in the current set that are not in the set pointed to by the argument set; that is, remove each element of the specified set from the current filter. Subtraction era. ➖

---

🎀 RETURN VALUE 🎀

Upon successful completion, these functions shall return a value of zero. Otherwise, they shall return the corresponding error number. Zero is the slay, anything else is a cry. 😭

The posix_trace_get_filter() function stores the set of filtered trace event types in set, if successful. Only if successful, bestie. Don't count on it otherwise. 🙈

---

💜 ERRORS 💜

These functions shall fail if:

• EINVAL — The value of the trid argument does not correspond to an active trace stream or the value of the argument pointed to by set is invalid.
• EINTR — The operation was interrupted by a signal.

The following sections are informative. (iykyk — informational only, not the binding part)

---

🌈 EXAMPLES 🌈

None. 😌 Nothing to show, we're keeping it mysterious.

---

🍓 APPLICATION USAGE 🍓

None. Same energy, same emptiness. ✨

---

🧚 RATIONALE 🧚

None. The reasoning is between the standards body and the void. 💫

---

⭐ FUTURE DIRECTIONS ⭐

The posix_trace_get_filter() and posix_trace_set_filter() functions may be removed in a future version. So like… cherish them while they're here. 🥲

---

👑 SEE ALSO 👑

• Table 2-4, Trace and Trace Event Filter Options: System Trace Events
• Table 2-6, Trace, Trace Log, and Trace Event Filter Options: System Trace Events
• posix_trace_eventset_add()
• The Base Definitions volume of POSIX.1‐2017, <trace.h>

---

📜 COPYRIGHT 📜

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

and that's the whole page, bestie 💖 this lil' legend came to you courtesy of IEEE/The Open Group, dated 2017, and the page is POSIX_TRACE_GET_FILTER(3P). go forth and filter responsibly, mwah 💅✨