You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*Edit: This doc request is for .net 8+, where the runtime and diagnostics added dotnet-gcdump support for mobile devices.
dotnet-dsrouter add some useful command to make mobile device interaction more conveniently, such as the dotnet-dsrouter android command.
The instructions provided by current document works fine when the default ip address is free, (checking the source code, it is 127.0.0.1:9000 by default), but there will be cases that port 9000 is occupied by other process, such as firm-wise internal security application, which one is not able or hard to alter.
Under such scenario, when working with dotnet-gcdump, the dotnet-dsrouter setup instructions provided with dotnet-dsrouter, dotnet-gcdump are not working.
By browsing the source code of dotnet-dsrouter and manual testing, the actually working dotnet-dsrouter config (manually checked with android device) is dotnet-dsrouter server-server -tcps 127.0.0.1:{port} -fp Android, with no ipcs option. If ipcs option added, dotnet-gcdump will not be able to collect the gcdump from mobile device, but only the dotnet-dsrouter's.
I only checked the work-around with android device though.
Please verify the work-around and consider add documentation for such scenario.
The text was updated successfully, but these errors were encountered:
*Edit: This doc request is for .net 8+, where the runtime and diagnostics added dotnet-gcdump support for mobile devices.
dotnet-dsrouter add some useful command to make mobile device interaction more conveniently, such as the
dotnet-dsrouter android
command.The instructions provided by current document works fine when the default ip address is free, (checking the source code, it is 127.0.0.1:9000 by default), but there will be cases that port 9000 is occupied by other process, such as firm-wise internal security application, which one is not able or hard to alter.
Under such scenario, when working with dotnet-gcdump, the dotnet-dsrouter setup instructions provided with dotnet-dsrouter, dotnet-gcdump are not working.
By browsing the source code of dotnet-dsrouter and manual testing, the actually working dotnet-dsrouter config (manually checked with android device) is
dotnet-dsrouter server-server -tcps 127.0.0.1:{port} -fp Android
, with no ipcs option. If ipcs option added, dotnet-gcdump will not be able to collect the gcdump from mobile device, but only the dotnet-dsrouter's.I only checked the work-around with android device though.
Please verify the work-around and consider add documentation for such scenario.
The text was updated successfully, but these errors were encountered: