Due to the requirement of the diagnostics server and how it expects strings to be encoded, I am crudely converting from char to uint16_t by straight casts. We may have to revisit in unicode scenarios.
We may in a later change include a flag (such as forcegcore) to bypass the diagnostics server for .net core processes. Not sure how viable that scenario is but we'll see.
The diagnostics socket path is either in $TMPDIR or hardcoded /tmp. If a user has $TMPDIR defined she will have to run sudo -E <procdump ....> in order for procdump to see the TMPDIR env variable.
… more manageable core dump sizes
A few notes on this PR:
Due to the requirement of the diagnostics server and how it expects strings to be encoded, I am crudely converting from char to uint16_t by straight casts. We may have to revisit in unicode scenarios.
We may in a later change include a flag (such as forcegcore) to bypass the diagnostics server for .net core processes. Not sure how viable that scenario is but we'll see.
The diagnostics socket path is either in $TMPDIR or hardcoded /tmp. If a user has $TMPDIR defined she will have to run sudo -E <procdump ....> in order for procdump to see the TMPDIR env variable.