python / python/cpython

Undefined C behavior going beyond end of struct via a [1] arrays (C99 flexible arrays)

Open
#84,301 28 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.11 build interpreter-core
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 40120
Nosy @gpshead, @pitrou, @vstinner, @serhiy-storchaka, @colesbury, @pablogsal
PRs
  • python/cpython#19232
  • 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 = 'https://github.com/gpshead'
    closed_at = None
    created_at = <Date 2020-03-30.21:04:23.697>
    labels = ['interpreter-core', 'build', '3.11']
    title = 'Undefined C behavior going beyond end of struct via a [1] arrays.'
    updated_at = <Date 2022-01-21.23:32:19.727>
    user = 'https://github.com/gpshead'
    

    bugs.python.org fields:

    activity = <Date 2022-01-21.23:32:19.727>
    actor = 'gregory.p.smith'
    assignee = 'gregory.p.smith'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2020-03-30.21:04:23.697>
    creator = 'gregory.p.smith'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 40120
    keywords = ['patch']
    message_count = 20.0
    messages = ['365349', '365350', '365399', '365403', '365410', '365415', '365425', '365464', '365465', '365466', '365472', '365539', '365671', '365691', '365744', '365745', '366883', '411151', '411168', '411207']
    nosy_count = 6.0
    nosy_names = ['gregory.p.smith', 'pitrou', 'vstinner', 'serhiy.storchaka', 'colesbury', 'pablogsal']
    pr_nums = ['19232']
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'compile error'
    url = 'https://bugs.python.org/issue40120'
    versions = ['Python 3.11']
    

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    Research direction

    Start by reviewing the migrated bugs.python.org issue 40120 and the referenced PR python/cpython#19232. Trace the CPython interpreter-core/build code involving C99 [1] arrays, then verify that the undefined behavior described in the issue is eliminated without introducing new build or interpreter failures.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    c, python
    Domain
    build-system, compilers
    Issue type
    Bug
    Difficulty
    4/5
    Estimated time
    3-5 days
    Activity status
    Stale
    Clarity
    Needs clarification
    Newbie friendliness
    15/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.