Currently only the Client command on the main thread is printed out on crash report. But, with modules many of the commands are running in a background thread and are not printed out.

Comment From: oranagra

so you want redis to iterate over all the blocked clients and print them and their command? in many cases like BLPOP, it's probably pointless (redis doesn't run any logic on behalf of that client). maybe the right approach is for the module to use this in order to log it's state and what it's currently processing:

typedef void (*RedisModuleInfoFunc)(RedisModuleInfoCtx *ctx, int for_crash_report);

Comment From: gkorland

Even in BLPOP I don't think it's pointless, the crash report should give us as much information as possible. Including currently blocking commands.