New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tool: add undocumented option --dump-module-paths for win32 #3208

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@jay
Member

jay commented Nov 1, 2018

  • Add an undocumented diagnostic option to show the full paths of all
    loaded modules regardless of whether or not libcurl initialization
    succeeds.

This is needed so that in the CI we can get a list of all DLL
dependencies after initialization (when they're most likely to have
finished loading) and then package them as artifacts so that a
functioning build can be downloaded. Also I imagine it may have some use
as a diagnostic for help requests.

Ref: #3103

Closes #xxxx


Something like this is needed to get the artifacts from the CI as discussed in #3103. I can't think of a better way to do it other than we add something to the tool and check after initialization, otherwise we're just guessing.

tool: add undocumented option --dump-module-paths for win32
- Add an undocumented diagnostic option to show the full paths of all
  loaded modules regardless of whether or not libcurl initialization
  succeeds.

This is needed so that in the CI we can get a list of all DLL
dependencies after initialization (when they're most likely to have
finished loading) and then package them as artifacts so that a
functioning build can be downloaded. Also I imagine it may have some use
as a diagnostic for help requests.

Ref: #3103

Closes #xxxx
@bagder

bagder approved these changes Nov 1, 2018

👍

We can document it later down the line if it turns out useful and a good thing.

@jay jay closed this in 397664a Nov 6, 2018

@jay jay deleted the jay:dump-module-paths branch Nov 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment