For_debugging (p.async.v0.17.0.doc.async.async_rpc.Async_rpc.Rpc.For

Async
- CHANGES
- LICENSE
- README
- Library async
  - Async
- Library async.async_command
  - Async_command
- Library async.async_quickcheck
  - Async_quickcheck
- Library async.async_rpc
  - Async_rpc
    - Rpc
    - Versioned_rpc
- Library async.lock_file_async
  - Lock_file_async
- Library async.log_extended
  - Log_extended
- Library async.persistent_connection
  - Persistent_connection
- Library async.unpack_sequence
  - Unpack_sequence
- Sources

val enable_dumping_buffers_on_deserialization_errors : 
  ?path_override:Core.Filename.t ->
  unit ->
  unit

If called, then when a message is not the expected length, or when bin_io deserialization fails, dump the buffer being read to a file under /dev/shm for later debugging. The default is to not dump any buffers in these cases. The file may be overridden by passing path_override

This is intended to be enabled in the background to debug applications that are occasionally seeing apparent message corruption, to help debug. It can also be enabled by setting the ASYNC_RPC_DEBUG_DUMP_DESERIALIZATION_ERRORS environment variable, in which case errors will be written to the path specified by the env var (relative to /dev/shm if the path contains no ‘/’).