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

Python3.3 segfaults when using big5hkscs encoding #64711

Closed
alexisd mannequin opened this issue Feb 4, 2014 · 6 comments
Closed

Python3.3 segfaults when using big5hkscs encoding #64711

alexisd mannequin opened this issue Feb 4, 2014 · 6 comments
Labels
type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@alexisd
Copy link
Mannequin

alexisd mannequin commented Feb 4, 2014

BPO 20512
Nosy @loewis, @vstinner, @ned-deily, @bitdancer, @1st1
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-02-04.21:51:03.596>
    created_at = <Date 2014-02-04.18:48:23.519>
    labels = ['type-crash']
    title = 'Python3.3 segfaults when using big5hkscs encoding'
    updated_at = <Date 2014-02-04.21:51:03.553>
    user = 'https://bugs.python.org/alexisd'

    bugs.python.org fields:

    activity = <Date 2014-02-04.21:51:03.553>
    actor = 'ned.deily'
    assignee = 'none'
    closed = True
    closed_date = <Date 2014-02-04.21:51:03.596>
    closer = 'ned.deily'
    components = []
    creation = <Date 2014-02-04.18:48:23.519>
    creator = 'alexis.d'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 20512
    keywords = []
    message_count = 6.0
    messages = ['210258', '210260', '210261', '210262', '210263', '210271']
    nosy_count = 6.0
    nosy_names = ['loewis', 'vstinner', 'ned.deily', 'r.david.murray', 'alexis.d', 'yselivanov']
    pr_nums = []
    priority = 'normal'
    resolution = 'duplicate'
    stage = 'resolved'
    status = 'closed'
    superseder = '18458'
    type = 'crash'
    url = 'https://bugs.python.org/issue20512'
    versions = ['Python 3.3']

    @alexisd
    Copy link
    Mannequin Author

    alexisd mannequin commented Feb 4, 2014

    When using the 'big5hkscs' encoding it's possible to make Python3.3 segfault, here is how to repro:

     ✗ 13:41 adaboville @ adoboville-mbp in ~ $ py3
    Python 3.3.2 (v3.3.2:d047928ae3f6, May 13 2013, 13:52:24)
    [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
    Type "help", "copyright", "credits" or "license" for more information.
    >>> 'nb'.encode('big5hkscs')
    b'nb'
    >>> 'nb'.encode('big5hkscs')
    Segmentation fault: 11

    Note that it doesn't crash on the first first line, but on the second (even though both lines are the same). FWIW pypy3.3 doesn't crash:

     ✓ 13:43 adaboville @ adoboville-mbp in .../pypy3-2.1-beta1-osx64 $ bin/pypy
    Python 3.2.3 (d63636b30cc0, Jul 30 2013, 07:02:48)
    [PyPy 2.1.0-beta1 with GCC 4.2.1 Compatible Clang Compiler] on darwin
    Type "help", "copyright", "credits" or "license" for more information.
    And now for something completely different: ``why did you guys have to make the
    builtin fortune more interesting than actual work? i just catched myself
    restarting pypy 20 times''
    >>>> 'nb'.encode('big5hkscs')
    b'nb'
    >>>> 'nb'.encode('big5hkscs')
    b'nb'
    >>>>

    @alexisd alexisd mannequin added the type-crash A hard crash of the interpreter, possibly with a core dump label Feb 4, 2014
    @1st1
    Copy link
    Member

    1st1 commented Feb 4, 2014

    Can't reproduce this on 3.3.3

    Python 3.3.3 (default, Dec 2 2013, 01:40:21)
    [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.2.79)] on darwin

    @bitdancer
    Copy link
    Member

    Alexis: are you on 10.9, by any chance?

    @alexisd
    Copy link
    Mannequin Author

    alexisd mannequin commented Feb 4, 2014

    @david: yes, 10.9.

    @bitdancer
    Copy link
    Member

    Most likely, then, this is a duplicate of bpo-18458.

    @ned-deily
    Copy link
    Member

    This is definitely a duplicate of bpo-18458 since the build signature indicates you are using 3.3.2 from the python.org OS X binary installer. The problem is fixed in the current Python 3.3.3 installer.

    @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

    3 participants