weak_ptr reset affects shared_ptr?

Question

I'm not very used to using weak_ptr and I'm facing a quite confusing situation. I'm using Intel XE 2019 Composer update 5 (package 2019.5.281) in combinaison with Visual Studio 2019 ver. 16.2.5. I compile in 64-bit. I use the standard C++ 17.

Here is the code for my spike solution:

#include <memory>
#include <iostream>

using namespace std;

int main( int argc, char* argv[] )
{
    shared_ptr<int> sp = make_shared<int>( 42 );
    cout << "*sp = " << *sp << endl;

    weak_ptr<int> wp = sp;
    cout << "*sp = " << *sp << ", *wp = " << *wp.lock() << endl;

    wp.reset();
    cout << "*sp = " << *sp << endl;

    return 0;
}

The output I expected to have is:

*sp = 42
*sp = 42, *wp = 42
*sp = 42

...but here is what I obtained:

*sp = 42
*sp = 42, *wp = 42
*sp = -572662307

What is goin on? Is it normal for the shared_ptr to be modified/invalidated when the/an associated weak_ptr is reset? I'm a little confused about the results I obtained. To say the truth I didn't expect this result...

EDIT 1

While the bug occurs in 64-bit configuration, it doesn't in 32-bit. In this later configuration, the result is what is expected.

EDIT 2

The bug occurs only in Debug. When I build in Release, I get the expected result.

Answer 1

It appears it is a real bug on Intel ICC side; I have reported it.

Thanks again for helping me to pin-point this problem.