Boost C++ Libraries: Ticket #8586: Boost Thread .join() causes exception. Intel C++ 13.1.1. Windows XP SP3

owner, status, description changed

viboes — Sun, 19 May 2013 14:11:45 GMT

owner changed from Anthony Williams to viboes
status new → assigned
description modified (diff)

viboes — Sun, 19 May 2013 14:15:17 GMT

Could you report the stack from where the exception is thrown?

viboes — Sun, 19 May 2013 14:42:35 GMT

Does it works for Intel 12.x?

Mon, 20 May 2013 08:36:23 GMT

Replying to viboes:

Does it works for Intel 12.x?

Hello, I compiled this example on Intel 12.0.1 too, same results for all four versions of boost I used before:

Thread_Boost1.53.0_ICC13.1.1.exe - bug
Thread_Boost1.52.0_ICC13.1.1.exe - bug
Thread_Boost1.51.0_ICC13.1.1.exe - works fine
Thread_Boost1.48.0_ICC13.1.1.exe - works fine
Thread_Boost1.53.0_ICC12.0.1.exe - bug
Thread_Boost1.52.0_ICC12.0.1.exe - bug
Thread_Boost1.51.0_ICC12.0.1.exe - works fine
Thread_Boost1.48.0_ICC12.0.1.exe - works fine

It's ok if I provide executable files for all results? You can grab it here: http://rghost.ru/46127334. I tried to debug Thread_Boost1.53.0_ICC13.1.1.exe in OllyDBG and that what I got: http://i.imgur.com/VyDtVL1.png. I hope it helps. Please tell me if you need more information from me.

viboes — Mon, 20 May 2013 09:18:03 GMT

No the executables are of any use. However the fact that both version match the results mean that the problem should come from an evolution on Boost 1.52 that doesn't works correctly with Intel compiler.

I was expecting a symbolic stack :( This is a must to take care of a crash.

Could you tell me if adding a sleep on the thread function avoid the crash?

Mon, 20 May 2013 11:29:20 GMT

Replying to viboes:

No the executables are of any use. However the fact that both version match the results mean that the problem should come from an evolution on Boost 1.52 that doesn't works correctly with Intel compiler.

I was expecting a symbolic stack :( This is a must to take care of a crash.

I tried to get call stack and what I got:

When I attach to process after exception - http://i.imgur.com/ke7ze5v.png
When I start to debug process from beginning - http://i.imgur.com/uvFO9k8.png

I'm sorry if it's might be not helpful, I use Visual Studio very rare, so I'm not very experienced in it.

Could you tell me if adding a sleep on the thread function avoid the crash?

I tried to add this code

boost::this_thread::sleep_for(boost::chrono::milliseconds(10000));

after "Hello from thread!" message, but no difference, still crashes.

viboes — Mon, 20 May 2013 14:39:18 GMT

Replying to Alexey <lakmus@…>:

Replying to viboes:

No the executables are of any use. However the fact that both version match the results mean that the problem should come from an evolution on Boost 1.52 that doesn't works correctly with Intel compiler.

I was expecting a symbolic stack :( This is a must to take care of a crash.

I tried to get call stack and what I got:

When I attach to process after exception - http://i.imgur.com/ke7ze5v.png

Thanks for this execution context. Could you show the complete symbolic stack?

When I start to debug process from beginning - http://i.imgur.com/uvFO9k8.png
I'm sorry if it's might be not helpful, I use Visual Studio very rare, so I'm not very experienced in it.

Could you tell me if adding a sleep on the thread function avoid the crash?

I tried to add this code
boost::this_thread::sleep_for(boost::chrono::milliseconds(10000));
after "Hello from thread!" message, but no difference, still crashes.

OK. At lest we know it is around the thread destruction.

Mon, 20 May 2013 16:23:02 GMT

Replying to viboes:

Thanks for this execution context. Could you show the complete symbolic stack?

I'm not sure where is complete symbolic stack in MSVS, but I managed to dig this windows when I loaded pdb information in debugger:

http://i.imgur.com/SBGlCOp.png

http://i.imgur.com/Ys8taGg.png

Is this helpful?

viboes — Tue, 21 May 2013 22:52:59 GMT

Replying to Alexey <lakmus@…>:

Replying to viboes:

Thanks for this execution context. Could you show the complete symbolic stack?

I'm not sure where is complete symbolic stack in MSVS, but I managed to dig this windows when I loaded pdb information in debugger:

http://i.imgur.com/SBGlCOp.png

http://i.imgur.com/Ys8taGg.png

Is this helpful?

Not too much :(

viboes — Sat, 03 Aug 2013 13:56:34 GMT

I don't reach to reproduce the error. Please, could you try defining BOOST_THREAD_DONT_USE_ATOMIC?

Sat, 03 Aug 2013 17:09:26 GMT

Replying to viboes:

I don't reach to reproduce the error. Please, could you try defining BOOST_THREAD_DONT_USE_ATOMIC?

Still receive an error.

viboes — Sun, 04 Aug 2013 09:07:31 GMT

Could you try dynamic allocation?

int main()
{
    boost::thread* my_thread = new boost::thread(&hello_world);
    my_thread->join();
    delete my_thread;
}

and also

int main()
{
    boost::thread my_thread(&hello_world);
    boost::this_thread::sleep_for(boost::chrono::milliseconds(10000));
    my_thread.join();
}

Sun, 04 Aug 2013 10:07:57 GMT

Replying to viboes:

int main()
{
    boost::thread* my_thread = new boost::thread(&hello_world);
    my_thread->join();
    delete my_thread;
}

Still error.

int main()
{
    boost::thread my_thread(&hello_world);
    boost::this_thread::sleep_for(boost::chrono::milliseconds(10000));
    my_thread.join();
}

Error after 10 sec. With BOOST_THREAD_DONT_USE_ATOMIC both results are the same too.

summary changed

viboes — Tue, 17 Sep 2013 05:21:10 GMT

summary Boost Thread .join() causes exception → Boost Thread .join() causes exception. Intel C++ 13.1.1. Windows XP SP3

viboes — Tue, 17 Sep 2013 21:20:15 GMT

Isn't this a duplicate of #7666?

status changed; resolution set

viboes — Tue, 17 Sep 2013 21:21:35 GMT

status assigned → closed
resolution → duplicate

viboes — Thu, 19 Sep 2013 22:09:15 GMT

With which options was built Boost? Please show the result of bjam with -d2 option

bjam toolset="intel" ---build-type=complete threading=multi link=static runtime-link=static -d2

And your program?

What is the size of boost::detail::thread_data_base on your program? And in a Boost.Thread test?

viboes — Thu, 26 Sep 2013 18:01:22 GMT

I suspect that this is related to an ABI incompatibility.