GNU nano - Bugs: bug #63520, nano crashes with code 11 when...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63520: nano crashes with code 11 when linting certain files
Submitter: | Anton <barankignu> | ||
Submitted: | Tue 13 Dec 2022 01:40:23 PM UTC | ||
Severity: | 4 - Important | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Open |
Jump to the original submission
Sun 04 Jun 2023 04:50:30 PM UTC, comment #6: |
Benno Schulenberg <bens>![]() ![]() |
Sun 04 Jun 2023 03:18:43 PM UTC, comment #5: Thanks for the file -- with it I can reproduce the crash when using nano-4.8. And it crashes up to nano-5.8. From version 5.9 onward, nano no longer crashes when invoking the linter (`gcc -fsyntax-only`) on this file. Just by looking at the commits, though, I cannot figure out which commit fixed the issue.
|
Benno Schulenberg <bens>![]() ![]() |
Sun 04 Jun 2023 11:47:50 AM UTC, comment #4: Added an attachment. |
Anton <barankignu> |
Wed 21 Dec 2022 10:53:26 AM UTC, comment #3: Closing, due to lack of response. |
Benno Schulenberg <bens>![]() ![]() |
Thu 15 Dec 2022 08:08:04 AM UTC, comment #2: To reword my response: I cannot reproduce the crash. Can you reproduce it yourself? If yes, then please post detailed reproduction steps. |
Benno Schulenberg <bens>![]() ![]() |
Tue 13 Dec 2022 03:23:32 PM UTC, comment #1: For me to be able to reproduce this, you will need to provide the file that you run the linter on. Because with 'extendsyntax c linter gcc -fsyntax-only' and introducing two syntax errors in src/cut.c and then running the linter on it, I can move through the messages (and try to go beyond first and last) just fine, without nano crashing. Even when using nano-4.8. |
Benno Schulenberg <bens>![]() ![]() |
Tue 13 Dec 2022 01:40:23 PM UTC, original submission:
nano 4.8 crashes with code 11 reaching end of linter messages
|
Anton <barankignu> |
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 11 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-06-07 | bens | Status | Confirmed | ![]() |
Fixed |
Assigned to | None | ![]() |
bens | ||
2023-06-04 | bens | Severity | 3 - Normal | ![]() |
4 - Important |
Status | Invalid | ![]() |
Confirmed | ||
Open/Closed | Closed | ![]() |
Open | ||
Summary | crashes with code 11 reaching end of linter messages | ![]() |
nano crashes with code 11 when linting certain files | ||
2023-06-04 | bens | Status | Need Info | ![]() |
Invalid |
2023-06-04 | barankignu | Carbon-Copy | Removed 338027 | ![]() |
- |
2023-06-04 | barankignu | Attached File | - | ![]() |
Added code11.c, #54809 |
2022-12-21 | bens | Open/Closed | Open | ![]() |
Closed |
2022-12-13 | bens | Status | None | ![]() |
Need Info |
Hrrmm... Somehow nano-5.9 and later do not crash on my usual machine, but on another machine (with the same distro as you are using) all released versions of nano crash. :/
However, commit b8ead3b5 ("linter: use a format string, to deflect format-string attacks") from a good two months ago has fixed the issue. This fix will be in the next release. Thanks for reporting.