On Mon, Apr 11, 2016 at 12:07:48AM +0300, Serhiy Storchaka wrote: > On 10.04.16 19:51, Jon Ribbens wrote: > >On Sun, Apr 10, 2016 at 02:51:23PM +1000, Nick Coghlan wrote: > >>On 9 April 2016 at 22:43, Victor Stinner <victor.stin...@gmail.com> wrote: > >>>See pysandbox test suite for a lot of ways to escape a sandbox. CPython has > >>>a list of know code to crash CPython (I don't recall the dieectory in > >>>sources), even with the latest version of CPython. > >> > >>They're at https://hg.python.org/cpython/file/tip/Lib/test/crashers > > > >Thanks. I take your point that sandboxing Python requires CPython to > >free of code execution bugs. However I will note that none of the > >crashers in that directory will work inside my experiment (except > >"infinite_loop_re.py", which isn't a crasher just a long loop). > > Try following example: > > it = iter([1]) > for i in range(1000000): > it = filter(None, it) > next(it)
That does indeed segfault. I guess you should report that as a bug! _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
