tdoherty Posted May 22, 2014 Report Share Posted May 22, 2014 Hello all, I've recently created a vary large model and I have encounted an assertion violation in sc_cor_qt::stack_protect. The mprotect system call returns a -1 value, triggering the assertion. The errno is ENOMEM. There is no memory allcoated expilicitly in stack_protect so it must mean that the address passed to mprotect is invalid. If I remove the stack_protect call from sc_thread_process::prepare_for_simulation then my model runs just fine. So it appears that stack_protect is not strictly needed, but probably a good idea to leave it in if you can. Anyone else ever have any problems with the stack_protect call? Thanks, Terry Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.