
24 Feb
2013
24 Feb
'13
6:03 p.m.
Oliver Kowalke wrote:
I'm wondering why a simple assignement of excpetion_ptr causes a segmentation fault if future's implementation uses intrusive_ptr + atomic + sequential - consistent ops instead of shared_ptr.
What does valgrind say? This sort of crash is often an indication that the shared_ptr memory has been corrupted.