GNU nano - Bugs: bug #57934, writing a new file makes use of...
You are not allowed to post comments on this tracker with your current authentication level.
bug #57934: writing a new file makes use of some uninitialized memory
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Sun 01 Mar 2020 04:20:25 PM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Sun 01 Mar 2020 06:36:01 PM UTC, comment #1: |
Benno Schulenberg <bens> |
Sun 01 Mar 2020 04:20:25 PM UTC, original submission:
When writing to a new, nonexistent file, valgrind compains about unitialized memory.
|
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.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-03-25 | bens | Open/Closed | Open | Closed | |
2020-03-02 | bens | Summary | writing a new file complains about uninitialized memory | writing a new file makes use of some uninitialized memory | |
2020-03-01 | bens | Assigned to | None | bens | |
2020-03-01 | bens | Status | In Progress | Fixed | |
2020-03-01 | bens | Status | None | In Progress | |
2020-03-01 | bens | Summary | writing a new file complains about unitialized memory | writing a new file complains about uninitialized memory |
Powered by Savane 3.13-02a9.
Corresponding source code
Fixed in git, commit 6c34ae58.
(The problem existed since commit e8e30e51 from June last year.)