>From reading what you've sent, I guess that what you have in mind is calling mmap with PROT_NONE and then calling mprotect() to change that to read/write whenever growing the stack? That seems like it might be a reasonable thing to do (though I'm only basing that on spending a few minutes reading what you sent, not from any actual knowledge that I had before).
I'm willing to devote some time (not today) to figuring out what the right thing to do is (maybe the above is already the right thing) / implementing this / reviewing this. On Mon, Sep 19, 2016 at 7:31 PM, Jeroen Demeyer <[email protected]> wrote: > After spending some time reading on the subject, I think I might have a > solution to this "problem". It involves calling mmap() with PROT_NONE, > which will require a patch to upstream PARI. > > However, before implementing this, I would like a *strong commitment* from > somebody to review my patch when I'm finished. Otherwise I'm just wasting > my time. > > > -- > You received this message because you are subscribed to the Google Groups > "sage-support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-support. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
