bugGNU nano - Bugs: bug #57724, if there were an error while...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #57724: if there were an error while writing a lock file, nano would crash

Submitter:  Benno Schulenberg <bens>
Submitted:  Sun 02 Feb 2020 09:42:56 AM UTC
 
Severity:  4 - Important Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Sun 02 Feb 2020 10:10:52 AM UTC, comment #1: 

Fixed in git, commit 74f4c37d.

Benno Schulenberg <bens>
Project Administrator
Sun 02 Feb 2020 09:42:56 AM UTC, original submission:  

In src/files.c, in write_lockfile(), if the fwrite() does not succeed in writing all 1024 bytes, and if then ferror() returns anything other than zero, nano would most likely crash, because the returned number would not be a pointer into nano's memory.

Benno Schulenberg <bens>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by bens (Submitted the item)
  •  

    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 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-02-09 bens Open/ClosedOpen Closed
    2020-02-02 bens Summaryif there were an error while writing a lockfile, nano would crash if there were an error while writing a lock file, nano would crash
    2020-02-02 bens StatusIn Progress Fixed

    Back to the top


    Powered by Savane 3.9