This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author berker.peksag
Recipients berker.peksag, larry, ned.deily, serhiy.storchaka, terry.reedy, vstinner, xiang.zhang
Date 2016-09-17.12:33:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474115590.34.0.701845610042.issue28179@psf.upfronthosting.co.za>
In-reply-to
Content
What do you mean by crash? I think the purpose of the test is to crash the interpreter:

    def test_recursionlimit_fatalerror(self):
        # A fatal error occurs if a second recursion limit is hit when recovering
        # from a first one.

        ...

        self.assertIn(
            b"Fatal Python error: Cannot recover from stack overflow",
            err)

test_sys passes for me in Python 3.5, but not in Python 3.6:

======================================================================
FAIL: test_recursionlimit_fatalerror (test.test_sys.SysModuleTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/berker/projects/cpython/default/Lib/test/test_sys.py", line 281, in test_recursionlimit_fatalerror
    err)
AssertionError: b'Fatal Python error: Cannot recover from stack overflow' not found in b''

----------------------------------------------------------------------

Running the snippet from msg276686 in Python 3.6:

    $ ./python -V
    Python 3.6.0b1+

    $ ./python a.py  
    Segmentation fault (core dumped)

In Python 3.5:

    $ ./python -V
    Python 3.5.2+

    $ ./python a.py 
    Fatal Python error: Cannot recover from stack overflow.

    Current thread 0x00007f5965eaf700 (most recent call first):
      File "a.py", line 5 in f
      File "a.py", line 5 in f
      File "a.py", line 5 in f
    [...]
History
Date User Action Args
2016-09-17 12:33:10berker.peksagsetrecipients: + berker.peksag, terry.reedy, vstinner, larry, ned.deily, serhiy.storchaka, xiang.zhang
2016-09-17 12:33:10berker.peksagsetmessageid: <1474115590.34.0.701845610042.issue28179@psf.upfronthosting.co.za>
2016-09-17 12:33:10berker.peksaglinkissue28179 messages
2016-09-17 12:33:10berker.peksagcreate