Skip to content

"Fatal Python error: Cannot recover from stack overflow." from pure Python code #73978

Closed

Description

@DavidMacIver
BPO 29792
Nosy @zhangyangyu
Superseder
  • bpo-6028: Interpreter aborts when chaining an infinite number of exceptions
  • Files
  • recursionerror.py
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2017-03-11.12:22:22.176>
    created_at = <Date 2017-03-11.11:33:02.131>
    labels = []
    title = '"Fatal Python error: Cannot recover from stack overflow." from pure Python code'
    updated_at = <Date 2017-03-11.12:28:32.136>
    user = 'https://bugs.python.org/DavidMacIver'

    bugs.python.org fields:

    activity = <Date 2017-03-11.12:28:32.136>
    actor = 'xiang.zhang'
    assignee = 'none'
    closed = True
    closed_date = <Date 2017-03-11.12:22:22.176>
    closer = 'David MacIver'
    components = []
    creation = <Date 2017-03-11.11:33:02.131>
    creator = 'David MacIver'
    dependencies = []
    files = ['46720']
    hgrepos = []
    issue_num = 29792
    keywords = []
    message_count = 3.0
    messages = ['289441', '289442', '289443']
    nosy_count = 2.0
    nosy_names = ['David MacIver', 'xiang.zhang']
    pr_nums = []
    priority = 'normal'
    resolution = 'duplicate'
    stage = 'resolved'
    status = 'closed'
    superseder = '6028'
    type = None
    url = 'https://bugs.python.org/issue29792'
    versions = ['Python 3.5', 'Python 3.6']

    Activity

    1. DavidMacIver commented on Mar 11, 2017

      DavidMacIvermannequin
      MannequinAuthor

      When run under Python 3.6.0 or 3.5.1 (and presumably other versions of Python 3) the attached code fails with "Fatal Python error: Cannot recover from stack overflow." then aborts with a core dump and an error code indicating it got a SIGABRT.

      On Python 2.7 it instead hangs indefinitely.

      Obviously this code is stupid and shouldn't be expected to do anything very reasonable - It's shrunk down from what was probably just a bug on my end in a larger example - but it seemed like it might be symptomatic of a more general class of problems.

    2. zhangyangyu commented on Mar 11, 2017

      @zhangyangyu
      Member

      Looks same as bpo-6028.

    3. DavidMacIver commented on Mar 11, 2017

      DavidMacIvermannequin
      MannequinAuthor

      So it does. My apologies. I'll close this.

    4. transferred this issue fromon Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      No labels
      No labels

      Projects

      No projects

        Milestone

        No milestone

        Relationships

        None yet

        Development

        No branches or pull requests

        Issue actions