Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable name with number causes interactive console to crash #65440

Closed
Cryvate mannequin opened this issue Apr 15, 2014 · 2 comments
Closed

Variable name with number causes interactive console to crash #65440

Cryvate mannequin opened this issue Apr 15, 2014 · 2 comments
Labels
type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@Cryvate
Copy link
Mannequin

Cryvate mannequin commented Apr 15, 2014

BPO 21241
Nosy @ned-deily, @cryvate
Superseder
  • bpo-18458: interactive interpreter crashes and test_readline fails on OS X 10.9 Mavericks due to libedit update
  • 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 2014-04-15.16:44:43.687>
    created_at = <Date 2014-04-15.16:41:05.867>
    labels = ['type-crash']
    title = 'Variable name with number causes interactive console to crash'
    updated_at = <Date 2014-04-15.16:44:43.687>
    user = 'https://github.com/cryvate'

    bugs.python.org fields:

    activity = <Date 2014-04-15.16:44:43.687>
    actor = 'ned.deily'
    assignee = 'none'
    closed = True
    closed_date = <Date 2014-04-15.16:44:43.687>
    closer = 'ned.deily'
    components = []
    creation = <Date 2014-04-15.16:41:05.867>
    creator = 'Cryvate'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 21241
    keywords = []
    message_count = 2.0
    messages = ['216334', '216335']
    nosy_count = 2.0
    nosy_names = ['ned.deily', 'Cryvate']
    pr_nums = []
    priority = 'normal'
    resolution = 'duplicate'
    stage = 'resolved'
    status = 'closed'
    superseder = '18458'
    type = 'crash'
    url = 'https://bugs.python.org/issue21241'
    versions = ['Python 3.3']

    @Cryvate
    Copy link
    Mannequin Author

    Cryvate mannequin commented Apr 15, 2014

    Executing in the interactive console: "foo1 = 0" and then "foo1" gives "Segmentation Fault: 11" on OS X 10.9.2, Python 3.3.2 (v3.3.2:d047928ae3f6, May 13 2013, 13:52:24)
    [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)]

    If foo1 is defined in a program, and interactive mode is entered, assigning a value to it seg faults the console as well, but executing "foo1" *does* work.

    It does not seem to crash problems on my friends PC (running Ubuntu).

    @Cryvate Cryvate mannequin added the type-crash A hard crash of the interpreter, possibly with a core dump label Apr 15, 2014
    @ned-deily
    Copy link
    Member

    See bpo-18458. Update to the latest Python 3.3.5 or 3.4.0.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    type-crash A hard crash of the interpreter, possibly with a core dump
    Projects
    None yet
    Development

    No branches or pull requests

    1 participant