Skip to content

Conversation

@jander-msft
Copy link
Contributor

These changes add a new command that provides the .NET runtime a path to a managed assembly that contains a startup hook. Issuing this command during diagnostic suspension would be similar to prepending the path to the DOTNET_STARTUP_HOOKS environment variable before launching the target process.

Corresponding runtime change: dotnet/runtime#86813

cc @dotnet/dotnet-monitor

Copy link
Contributor

@davmason davmason left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just the one thing and it looks good to me.

@davmason
Copy link
Contributor

@jander-msft are you waiting for the design to be approved before working on the runtime side, or did I miss a PR?

@jander-msft
Copy link
Contributor Author

@jander-msft are you waiting for the design to be approved before working on the runtime side, or did I miss a PR?

I'm actively working on it here: https://github.com/dotnet/runtime/pull/86813/files. Please provide any feedback you feel necessary. The intent is that the startup hook is cached during startup diagnostic suspension and applied when resumed; a follow up PR will enable automatically applying and executing the startup hook when managed code is already running.

@jander-msft
Copy link
Contributor Author

/azp run diagnostics-public-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jander-msft jander-msft merged commit d3fae1c into dotnet:main Jun 14, 2023
@jander-msft jander-msft deleted the applystartuphook branch June 14, 2023 03:02
@github-actions github-actions bot locked and limited conversation to collaborators Jan 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants