[Python-Dev] Re: PEP 651 -- Robust Overflow Handling

2021年1月19日 08:40:34 -0800

On 2021年1月19日 16:28:46 +0000
Mark Shannon <[email protected]> wrote:
> On 19/01/2021 4:15 pm, Antoine Pitrou wrote:
> > On 2021年1月19日 15:54:39 +0000
> > Mark Shannon <[email protected]> wrote: 
> >> On 19/01/2021 3:40 pm, Antoine Pitrou wrote: 
> >>> On 2021年1月19日 13:31:45 +0000
> >>> Mark Shannon <[email protected]> wrote: 
> >>>> Hi everyone,
> >>>>
> >>>> It's time for yet another PEP :)
> >>>>
> >>>> Fortunately, this one is a small one that doesn't change much.
> >>>> It's aim is to make the VM more robust. 
> >>>
> >>> On the principle, no objection.
> >>>
> >>> In practice, can you show how an implementation of Py_CheckStackDepth()
> >>> would look like? 
> >>
> >> It would depend on the platform, but a portable-ish implementation is here:
> >>
> >> https://github.com/markshannon/cpython/blob/pep-overflow-implementation/Include/internal/pycore_ceval.h#L71
> >> 
> > 
> > This doesn't tell me how `stack_limit_pointer` is computed or estimated
> > :-) 
> 
> It's nothing clever, and the numbers I've chosen are just off the top of 
> my head.
> 
> https://github.com/markshannon/cpython/blob/pep-overflow-implementation/Modules/_threadmodule.c#L1071
What about the main thread?
Is `stack_limit_pointer` some kind of thread-local? I suppose nothing
stops an OS to use different virtual addresses for the stacks of
different threads (especially if randomization of stack addresses is
desired).
Regards
Antoine.
_______________________________________________
Python-Dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/SKJMONH55RMKJNZVI4K7AVOIUOK77WZ7/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to