Generating debug information on demand

A system comprising:

• a memory to store a user script;
• and
• a processing device coupled to the memory to
• execute an introspection tool to monitor an execution of software, the software being executed using an executable of a software source code file, the software source code file being associated with one or more additional source files,
• detect a trigger in a user script pertaining to monitoring of the execution of the software, wherein the trigger comprises a variable type name or a tracepoint name,
• identify an additional source file that corresponds to the trigger by identifying the additional source file that corresponds to at least one of the tracepoint name or the variable type name,
• generate debug information describing a structure of the trigger by compiling the additional source file, wherein the debug information comprises at least one of functions for tracepoints that are defined in the software or information for more than one variable type name, and
• identify the structure specified in the debug information to respond to the trigger in the user script by searching the debug information for a tracepoint name that matches the tracepoint name in the trigger or searching the debug information for a variable type name that matches the variable type name in the trigger.

A non-transitory computer-readable storage medium including instructions that, when executed by a processing device, cause processing device to perform a set of operations comprising:

• monitoring an execution of software, the software being executed using an executable of a software source code file, the software source code file being associated with one or more additional source files;
• detecting a trigger in a user script pertaining to monitoring of the execution of the operating system, wherein the trigger comprises a variable type name or a tracepoint name;
• identifying an additional source file that corresponds to the trigger in the user script by identifying the additional source file that corresponds to at least one of the tracepoint name or the variable type name;
• generating, by the processing device, debug information describing a structure of the trigger by compiling the additional source file, wherein the debug information comprises at least one of functions for tracepoints that are defined in the software or information for more than one variable type name;
• and
• identifying the structure specified in the debug information to respond to the trigger in the user script by searching the debug information for a tracepoint name that matches the tracepoint name in the trigger or searching the debug information for a variable type name that matches the variable type name in the trigger.