bugGNU nano - Bugs: bug #48164, nano crashes when opening a file...

 
 

bug #48164: nano crashes when opening a file in a new buffer on OS X

Submitted by:  Dirkjan Ochtman <djc>
Submitted on:  Tue 07 Jun 2016 05:59:45 PM UTC  
 
Severity: 4 - ImportantStatus: Fixed
Assigned to: Benno Schulenberg <bens>Open/Closed: Closed

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Mon 20 Jun 2016 10:19:34 AM UTC, comment #4:

The fix was released. Thanks again for the report.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Sat 11 Jun 2016 12:03:54 PM UTC, comment #3:

Thanks for confirming that current git master works okay on OS X. Yes, this means that the next release will have this problem fixed.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Sat 11 Jun 2016 11:55:38 AM UTC, comment #2:

Thanks for the feedback. I built nano from the Git repository on my machine, from tag v2.5.3, and could reproduce the crash. I then rebuilt from master, and was no longer able to reproduce the crash; so I assume the next release will not have this problem?

Dirkjan Ochtman <djc>
Wed 08 Jun 2016 07:57:14 AM UTC, comment #1:

Hello Dirkjan,

If you compiled 2.5.3 yourself, then please try the four patches from https://lists.gnu.org/archive/html/nano-devel/2016-04/msg00075.html. Possibly one of those fixes the problem.

If not, try applying also the attached patch.

If still not fixed, see if 'nano --ignore ...' crashes too. If not, see what 'nano --syntax=none ...' does. If that doesn't crash either, then start nano normally, but before opening the second file, switch off syntax highlighting with M-Y. If also then it doesn't crash, we might have a cousin/duplicate of bug #48103, and that will become my next target.

If the five patches didn't help, please try building from git.

If gdb doesn't work, how does valgrind fare?

(file #37430)

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Tue 07 Jun 2016 05:59:45 PM UTC, original submission:

I found a crash in nano-2.5.3 on OS X (from homebrew).

When I open `nano src/ec/eddsa.rc`, then CTRL + R, ALT + F, `src/signature.rs`, Enter, I get the following message:

File to insert into new buffer [from ./] : src/signature.rsnano(21277,0x7fff79674000) malloc: *** error for object 0x7fa1ac0c3400: pointer being freed was not allocated ^X Execute Command ^T To Files
^C Cancel *** set a breakpoint in malloc_error_break to debug
Abort trap: 6

I tried to run gdb on it, but didn't succeed due to a lack of code signing.

Dirkjan Ochtman <djc>

 

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

Attach File(s):
   
   
Comment:
   

Attached Files

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by bens (Updated the item)
  • -unavailable- added by djc (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 7 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon 20 Jun 2016 10:19:34 AM UTCbensOpen/ClosedOpen=>Closed
      Summarycrash when opening a file in a new buffer on OS X=>nano crashes when opening a file in a new buffer on OS X
    Sat 11 Jun 2016 12:03:54 PM UTCbensStatusNone=>Fixed
    Wed 08 Jun 2016 07:57:14 AM UTCbensAttached File-=>Added 0005-dont-call-getcwd-with-null.patch, #37430
      Severity3 - Normal=>4 - Important
      Assigned toNone=>bens
      SummaryCrash when opening file in new buffer on OS X=>crash when opening a file in a new buffer on OS X

    Back to the top


    Powered by Savane 3.1-cleanup1