keywords, version, component changed

Mon, 09 Oct 2017 17:24:14 GMT

keywords context added
version Boost 1.63.0 → Boost 1.65.0
component coroutine → context

Hi,

I did some further investigations and can provide some more details. The problem also occurs in the newest boost release (1.65.1). The behavior is still the same. It only crashes when the C# debugger (without native debugging) is attached but I can directly reproduce it with context, the coroutine2 wrapper around it is not necessary.

This is the updated content of the Api.cpp file:

#include <boost/coroutine2/coroutine.hpp>
#include <boost/context/all.hpp>
class Foo
{
public:
	void bar() {
		throw std::exception("Hello World!");
	}
};
int ApiInit()
{
	boost::context::continuation source = boost::context::callcc(
		[](boost::context::continuation && sink) {
			Foo foo;
			try {
				foo.bar();
			}
			catch (const std::exception& ex) {
				std::cerr << "caught ex: " << ex.what() << std::endl;
			}
			return std::move(sink);
		});
	if (source.operator bool())
		source = source.resume();
	return 0;
}

It's important that this is compiled without optimizations enabled (e.g. in debug mode) so that throwing the exception won't be optimized away. Because the actual issue is exactly the process of throwing an exception.

Best Regards,

Michael

Thu, 30 Nov 2017 06:38:12 GMT

In a first quick test with boost 1.65.1 and windows fibers as implementation for boost-context I haven't been able to reproduce the issue anymore. My current suspision is that the .Net Debugger in some circumstances might use additional registers which are not backuped by the default fcontext implementation.

Boost C++ Libraries: Ticket #13245: Coroutines2: Crashes Visual Studio when attached with a debugger (on Windows x86)

keywords, version, component changed