Displaying 2 results from an estimated 2 matches for "print_debug_arg".
Did you mean:
print_debug_args
2023 Jun 12
1
[PATCH libnbd 2/2] generator: state machine: Be less verbose in debug messages
...> pr " case %s:\n" (c_string_of_external_event e);
> if state != next_state then (
> pr " set_next_state (h, %s);\n" next_state.parsed.state_enum;
> - pr " debug (";
> - let print_debug_args () =
> - pr "h, \"event %%s: %%s -> %%s\", ";
> - pr "\"%s\", \"%s\", \"%s\");"
> - (string_of_external_event e)
> - display_name next_state.parsed.display_n...
2023 Jun 12
3
[PATCH libnbd 0/2] Two simple patches
These patches aren't related to each other, but both are quite simple.
The second one requires particular attention - it's my experience that
printing out the state transitions in debug mode has never helped me
to diagnose a bug, but it has made the debug logs huge and hard to
follow. However that might just be me! Has it helped anyone else?
Also I'm open to the concept of debug