Changes between Version 3 and Version 4 of Ticket #12592, comment 5


Ignore:
Timestamp:
Jan 22, 2017, 6:26:07 PM (6 years ago)
Author:
olli

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #12592, comment 5

    v3 v4  
    1 I've had time to look at this bug report in more detail:
     1I've had time to look at this bug in more detail:
    22
    33The bottom stack is correctly aligned (16-byte) - the problem is that
    … …  
    55   execution_context<int> source([](execution_context<int> sink, int)
    66
    7 Uses the 'fixedsize_stack' with a default size of 64kB. That means that in best case you get an segmentation fault if you excceed the stack size (allocating 7 arrays on the stack).
     7uses the 'fixedsize_stack' with a default size of 64kB. That means that in best case you get an segmentation fault if you excceed the stack size (allocating 7 arrays on the stack).
    88
    99Windows does not provide segemented (on demand growing) stacks.
    1010
    11 If you use the 'protected_fixedsize_stack' you get an guard page appended. If you access memory fro m that page you get an 'stack overflow' exception (tested):
     11If you use the 'protected_fixedsize_stack' you get an guard page appended at the stack. If you access memory from that page an 'stack overflow' exception is raised:
    1212
    1313    execution_context<int> source(
    … …  
    1515             [](execution_context<int> sink, int)
    1616
    17 In your case you used the fixedsize_stack with a stack size of 64kb, which seams too small for your use case.
     17In your case you used the fixedsize_stack with a stack size of 64kb, which seams too small for your use case. You should try a larger stack size.
    1818
    1919So, I close this bug as 'works for me'.