GNU nano - Bugs: bug #62991, memory leak when a string bind...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62991: memory leak when a string bind specifies an unknown menu
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Wed 31 Aug 2022 07:31:54 AM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Wed 31 Aug 2022 02:48:20 PM UTC, comment #2: |
Benno Schulenberg <bens>![]() ![]() |
Wed 31 Aug 2022 02:40:33 PM UTC, comment #1: I had ordered the check for a valid menu name after the check for a valid function name, to have error messages go from left to right -- meaning that if an error was reported for somewhere in the line, that everything to the left of it was okay. But that has not been fully the case since the beginning, as the absence of a menu name gets reported before an invalid function name.
|
Benno Schulenberg <bens>![]() ![]() |
Wed 31 Aug 2022 07:31:54 AM UTC, original submission:
To reproduce, run:
Then type ^X. Result:
|
Benno Schulenberg <bens>![]() ![]() |
No files currently attached
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.
Fixed in git, commit 97fa42c8, by moving the menu-checking fragment to before the function-checking fragment.