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

3.11 exec raises SystemError instead of SyntaxError on char after line continuation #89901

Closed
pewscorner mannequin opened this issue Nov 6, 2021 · 12 comments
Closed
Labels
3.9 only security fixes 3.11 only security fixes type-bug An unexpected behavior, bug, or error

Comments

@pewscorner
Copy link
Mannequin

pewscorner mannequin commented Nov 6, 2021

BPO 45738
Nosy @aroberge, @Carreau, @lysnikolaou, @Zac-HD, @pablogsal, @miss-islington, @isidentical, @pewscorner
PRs
  • bpo-45738: Fix computation of error location for invalid continuation characters in the parser #29550
  • [3.10] bpo-45738: Fix computation of error location for invalid continuation (GH-29550) #29551
  • [3.9] bpo-45738: Fix computation of error location for invalid continuation (GH-29550) #29552
  • 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 2021-11-14.13:59:48.259>
    created_at = <Date 2021-11-06.13:10:51.997>
    labels = ['type-bug', '3.9', '3.11']
    title = '3.11 exec raises SystemError instead of SyntaxError on char after line continuation'
    updated_at = <Date 2021-11-14.18:39:21.628>
    user = 'https://github.com/pewscorner'

    bugs.python.org fields:

    activity = <Date 2021-11-14.18:39:21.628>
    actor = 'mbussonn'
    assignee = 'none'
    closed = True
    closed_date = <Date 2021-11-14.13:59:48.259>
    closer = 'pablogsal'
    components = []
    creation = <Date 2021-11-06.13:10:51.997>
    creator = 'pewscorner'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 45738
    keywords = ['patch']
    message_count = 12.0
    messages = ['405860', '406188', '406223', '406224', '406235', '406236', '406301', '406303', '406304', '406305', '406322', '406329']
    nosy_count = 8.0
    nosy_names = ['aroberge', 'mbussonn', 'lys.nikolaou', 'Zac Hatfield-Dodds', 'pablogsal', 'miss-islington', 'BTaskaya', 'pewscorner']
    pr_nums = ['29550', '29551', '29552']
    priority = 'normal'
    resolution = 'fixed'
    stage = 'resolved'
    status = 'closed'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue45738'
    versions = ['Python 3.9', 'Python 3.11']

    @pewscorner
    Copy link
    Mannequin Author

    pewscorner mannequin commented Nov 6, 2021

    When exec'ing code with an illegal character after the line continuation character '\', python 3.11.0a2 raises this strange exception:

    SystemError: Negative size passed to PyUnicode_New

    Here's an example where '#' is the illegal character:

      exec('1,\\#\n2')

    I expected the following exception (which is raised by Python 3.10.0, and also by Python 3.11.0a2 when using eval instead of exec, or when the string content is put into its own file and run as a normal script):

    SyntaxError: unexpected character after line continuation character

    @pewscorner pewscorner mannequin added 3.11 only security fixes type-bug An unexpected behavior, bug, or error labels Nov 6, 2021
    @Zac-HD
    Copy link
    Mannequin

    Zac-HD mannequin commented Nov 12, 2021

    It looks like this also affects Python 3.9.8, which makes me very suspicious of https://bugs.python.org/issue45494 as the probable cause.

    See Zac-HD/hypothesmith#16 and psf/black#2592 (comment) for reports.

    @Zac-HD Zac-HD mannequin added the 3.9 only security fixes label Nov 12, 2021
    @Carreau
    Copy link
    Mannequin

    Carreau mannequin commented Nov 12, 2021

    Yep, this also break IPython command completions when users press tab in some places in multiline code.

    88f4ec8 is the first offending commit for me in the 3.9 branch:

    [3.9] bpo-45494: Fix parser crash when reporting errors involving invalid continuation characters (GH-28993) (bpo-29071)
    
    There are two errors that this commit fixes:
    
    * The parser was not correctly computing the offset and the string
      source for E_LINECONT errors due to the incorrect usage of strtok().
    * The parser was not correctly unwinding the call stack when a tokenizer
      exception happened in rules involving optionals ('?', [...]) as we
      always make them return valid results by using the comma operator. We
      need to check first if we don't have an error before continuing..
    (cherry picked from commit a106343f632a99c8ebb0136fa140cf189b4a6a57)
    
    Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
    
    NOTE: unlike the cherry-picked original, this commit points at a crazy location
    due to a bug in the tokenizer that required a big refactor in 3.10 to fix.
    We are leaving as-is for 3.9.
    

    @Carreau
    Copy link
    Mannequin

    Carreau mannequin commented Nov 12, 2021

    Note that with the following example, exec and CommandCompiler return a different error:

        from codeop import CommandCompiler
    # identical errors
    #exec('1,\\#\n2') SystemError
    #CommandCompiler()('1,\\#\n2', symbol='exec') SystemError
    
        # one is syntax the other is System.
        exec('a \ \n')  # SyntaxError
        CommandCompiler()('a \ \n', symbol='exec') # SystemError

    @pablogsal
    Copy link
    Member

    I will be able to take a look later in the weekend, so if someone is able to give it a go before, that would be great.

    @Carreau
    Copy link
    Mannequin

    Carreau mannequin commented Nov 12, 2021

    I will be able to take a look later in the weekend

    Please take some time for yourself, I added you as you were the original author of the patch to make you aware. I believe most projects can workaround that for now.

    @pablogsal
    Copy link
    Member

    New changeset 25835c5 by Pablo Galindo Salgado in branch 'main':
    bpo-45738: Fix computation of error location for invalid continuation (GH-29550)
    25835c5

    @miss-islington
    Copy link
    Contributor

    New changeset bf26a6d by Miss Islington (bot) in branch '3.10':
    bpo-45738: Fix computation of error location for invalid continuation (GH-29550)
    bf26a6d

    @pablogsal
    Copy link
    Member

    This should be fixed by now, but please, check if everything is in order in your respective test suites and confirm here.

    @pablogsal
    Copy link
    Member

    New changeset 142fcb4 by Pablo Galindo Salgado in branch '3.9':
    bpo-45738: Fix computation of error location for invalid continuation characters in the parser (GH-29550) (GH-29552)
    142fcb4

    @pewscorner
    Copy link
    Mannequin Author

    pewscorner mannequin commented Nov 14, 2021

    Seems to work. Thanks!

    @Carreau
    Copy link
    Mannequin

    Carreau mannequin commented Nov 14, 2021

    Works for me as well. Thanks.

    @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
    3.9 only security fixes 3.11 only security fixes type-bug An unexpected behavior, bug, or error
    Projects
    None yet
    Development

    No branches or pull requests

    2 participants