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.

Sign up for GitHub

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

Jump to bottom

Undefined behavior in Parser/parsetok.c #78581

Closed
ZackerySpytz mannequin opened this issue Aug 14, 2018 · 9 comments
Closed

Undefined behavior in Parser/parsetok.c #78581

ZackerySpytz mannequin opened this issue Aug 14, 2018 · 9 comments
Labels
3.7 (EOL) end of life 3.8 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error

Comments

@ZackerySpytz
Copy link
Mannequin

ZackerySpytz mannequin commented Aug 14, 2018

BPO 34400
Nosy @benjaminp, @serhiy-storchaka, @ZackerySpytz, @miss-islington
PRs
  • bpo-34400: Fix undefined behavior in parsetok() #4439
  • [3.7] closes bpo-34400: Fix undefined behavior in parsetok(). (GH-4439) #8768
  • [3.6] closes bpo-34400: Fix undefined behavior in parsetok(). (GH-4439) #8769
  • [2.7] closes bpo-34400: Fix undefined behavior in parsetok(). (GH-4439) #8770
  • bpo-34400: Fix more undefined behavior in parsetok.c #8833
  • [3.7] bpo-34400: Fix more undefined behavior in parsetok.c (GH-8833) #8842
  • [3.6] bpo-34400: Fix more undefined behavior in parsetok.c (GH-8833) #8843
  • [2.7] bpo-34400: Fix more undefined behavior in parsetok.c (GH-8833). #8849
    		•

    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 2018-08-15.06:27:29.098>
created_at = <Date 2018-08-14.09:46:55.514>
labels = ['interpreter-core', '3.8', 'type-bug', '3.7']
title = 'Undefined behavior in Parser/parsetok.c'
updated_at = <Date 2018-08-22.05:54:21.764>
user = 'https://github.com/ZackerySpytz'

    bugs.python.org fields:

    activity = <Date 2018-08-22.05:54:21.764>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = True
closed_date = <Date 2018-08-15.06:27:29.098>
closer = 'benjamin.peterson'
components = ['Interpreter Core']
creation = <Date 2018-08-14.09:46:55.514>
creator = 'ZackerySpytz'
dependencies = []
files = []
hgrepos = []
issue_num = 34400
keywords = ['patch']
message_count = 9.0
messages = ['323505', '323548', '323549', '323551', '323553', '323813', '323814', '323815', '323863']
nosy_count = 4.0
nosy_names = ['benjamin.peterson', 'serhiy.storchaka', 'ZackerySpytz', 'miss-islington']
pr_nums = ['4439', '8768', '8769', '8770', '8833', '8842', '8843', '8849']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34400'
versions = ['Python 2.7', 'Python 3.6', 'Python 3.7', 'Python 3.8']
    @ZackerySpytz
    Copy link
    Mannequin Author

    ZackerySpytz mannequin commented Aug 14, 2018

    In parsetok(), null pointers are used in pointer arithmetic.

    @ZackerySpytz ZackerySpytz mannequin added 3.7 (EOL) end of life 3.8 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error labels Aug 14, 2018
    @benjaminp
    Copy link
    Contributor

    New changeset 7c4ab2a by Benjamin Peterson (Zackery Spytz) in branch 'master':
    closes bpo-34400: Fix undefined behavior in parsetok(). (GH-4439)
    7c4ab2a

    @miss-islington
    Copy link
    Contributor

    New changeset 2275b77 by Miss Islington (bot) in branch '3.7':
    closes bpo-34400: Fix undefined behavior in parsetok(). (GH-4439)
    2275b77

    @miss-islington
    Copy link
    Contributor

    New changeset 00aebab by Miss Islington (bot) in branch '2.7':
    closes bpo-34400: Fix undefined behavior in parsetok(). (GH-4439)
    00aebab

    @miss-islington
    Copy link
    Contributor

    New changeset 981aa46 by Miss Islington (bot) in branch '3.6':
    closes bpo-34400: Fix undefined behavior in parsetok(). (GH-4439)
    981aa46

    @benjaminp
    Copy link
    Contributor

    New changeset 3e26e42 by Benjamin Peterson (Zackery Spytz) in branch 'master':
    bpo-34400: Fix more undefined behavior in parsetok.c (GH-8833)
    3e26e42

    @miss-islington
    Copy link
    Contributor

    New changeset 985dcd4 by Miss Islington (bot) in branch '3.7':
    bpo-34400: Fix more undefined behavior in parsetok.c (GH-8833)
    985dcd4

    @miss-islington
    Copy link
    Contributor

    New changeset e496b2b by Miss Islington (bot) in branch '3.6':
    bpo-34400: Fix more undefined behavior in parsetok.c (GH-8833)
    e496b2b

    @serhiy-storchaka
    Copy link
    Member

    New changeset eb9a1c0 by Serhiy Storchaka (Zackery Spytz) in branch '2.7':
    [2.7] bpo-34400: Fix more undefined behavior in parsetok.c (GH-8833). (GH-8849)
    eb9a1c0

    @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
    Assignees
    No one assigned
    Labels
    3.7 (EOL) end of life 3.8 only security fixes interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Milestone
    No milestone
    Development

    No branches or pull requests
    3 participants
    @benjaminp @serhiy-storchaka @miss-islington