Aws::InitAPI(options) fails for release version dlls on Windows

[RoyZhang2022]

Hi,

We have some unit tests that uses AWS SDK C++ dlls on Windows. The code is like this. We build only components "core;rds;secretsmanager".

    static Aws::SDKOptions options;

    static void SetUpTestSuite() {
        Aws::InitAPI(options);
        ...
    }

I found the tests could work well with SDK dlls debug version when I build my tests as debug version. If I run my debug version test with SDK dlls release version, I always see an exception from Aws::InitAPI(options). The call stack is like this. I suppose my tests should run successfully no matter I am using release version or debug version SDK dlls. But now I always see this problem. Seems monitoringFactoryCreateFunctions is always a random value for SDK release version. Tried 1.11.21 and 1.11.190. Both have same problem. Is this a bug or something I need to pay attention?

My Windows info:

Edition	Windows 10 Pro
Version	22H2
Installed on	‎2022-‎05-‎03
OS build	19045.3636
Experience	Windows Feature Experience Pack 1000.19053.1000.0

Thanks,
Roy

[RoyZhang2022]

For debug version I found options.monitoringOptions.customizedMonitoringFactory_create_fn is 0.

[RoyZhang2022]

Just found the options.monitoringOptions.customizedMonitoringFactory_create_fn value is changed once Aws::InitAPI() is entered.

--options value at caller of Aws::InitAPI()

--options value once enter Aws::InitAPI()

Even I set options.monitoringOptions value manually it still has this error.

        Aws::MonitoringOptions monitoringOptions;
        options.monitoringOptions = monitoringOptions;
        Aws::InitAPI(options);

[jmklix]

Here are a few things that might fix the errors that you're seeing:

• Updating to the latest version of this sdk. This PR might have fixed the errors that you were seeing
• Check that the built and installed SDK version matches the version of the SDK headers
• adding {} when initializing options (i.e. static Aws::SDKOptions options = {};)

Please let us know if you are still running into errors when using this sdk