GNU nano - Bugs: bug #51550, doing replacements after invoking...
You are not allowed to post comments on this tracker with your current authentication level.
bug #51550: doing replacements after invoking the linter can result in a segfault
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Sun 23 Jul 2017 07:11:43 PM UTC | ||
Severity: | 4 - Important | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Wed 26 Jul 2017 07:34:08 PM UTC, comment #1: |
Benno Schulenberg <bens> |
Sun 23 Jul 2017 07:11:43 PM UTC, original submission:
Invoke the linter on the attached Python file. It finds something fishy on line 459. Type ^C, and then immediately follow this with: M-R pass <Enter> aha <Enter> A. Then type another A. See how the current line disappears (as if you typed ^K <Enter> in a single keystroke). What?! Try to undo this with: M-U. Result: segmentation fault. Boohoohoo!
|
Benno Schulenberg <bens> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-08-28 | bens | Open/Closed | Open | Closed | |
2017-07-26 | bens | Status | None | Fixed | |
Assigned to | None | bens | |||
2017-07-23 | bens | Attached File | - | Added robot.py, #41304 |
Powered by Savane 3.13-f8d8.
Corresponding source code
Fixed in git, c24432ed.
(The "offending" commit was 2439e1e4, from last April, which fixed bug #47131.)