PMPARSEDEBUG(3)

💖 PMPARSEDEBUG(3) — the library functions girlies 💖

okay so bestie, welcome to PMPARSEDEBUG(3), living in the Library Functions Manual section of the PCP docs. grab a snack, we're doing bit-fields 🍓

---

✨ NAME ✨

__pmParseDebug, __pmSetDebugBits — manipulate old-style PCP debugging control bit-fields 💅

---

🌸 C SYNOPSIS 🌸

#include <pcp/pmapi.h>
#include <pcp/deprecated.h>

int __pmParseDebug(const char *spec);
void __pmSetDebugBits(int value);

cc ... -lpcp

---

🦋 DESCRIPTION 🦋

ngl, these routines have been deprecated and may be removed in a future Performance Co-Pilot (PCP) release 😭 so please, for your own sake, go look at pmSetDebug(3) and pmClearDebug(3) for the replacement functionality. they're the glow-up versions, fr fr.

__pmParseDebug parses spec, and it's assuming that thing is a comma separated list of PCP debug flags. like a lil roster of flags, one after another 💖

each flag can be given as either an integer, or as the trailing portion of the symbolic name of the corresponding flag, exactly as reported by pmdbg(1). the symbolic names get stripped of the `DBG_TRACE_` prefix, and they can show up in either case — uppercase, lowercase, doesn't matter, it ate both ways 👑

special case alert 🚨 the values `-1` and `ALL` are treated as synonyms for turning on all bits except the sign bit in the result, i.e. INT_MAX from <limits.h>. iconic behaviour honestly.

for example: the debug option fetch is defined in the output from pmdbg(3) with the -L option, and it may be specified in spec as 2, FETCH or fetch. three ways, same vibe ✨

__pmSetDebugBits lets you set the bit-fields directly using the encoding in value. and listen, the effect is additive, so consecutive calls to __pmSetDebugBits will set the conjunction of the bits in the value arguments. they stack, bestie 📚 and if you wanna clear the bit-fields instead? see pmClearDebug(3) 🧚

---

💀 DIAGNOSTICS 💀

if it slays (i.e. succeeds), __pmParseDebug returns the value computed by the bit-wise `or` of each flag in the spec — perfect for assigning to the global debug trace control variable pmDebug 💖

otherwise the return value is less than 0, which is the code's way of saying "parsing error, girl" 😭

---

🫶 SEE ALSO 🫶

pmdbg(1), pmSetDebug(3) and pmClearDebug(3).

---

and that's the whole page, no cap 🎀 this one came to you from Performance Co-Pilot (PCP), filed under PMPARSEDEBUG(3) — go drink some water and clear your debug bits, ily 💜🦋🌸