[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-nano] Segfaults in libc-2.19 w/ 2.9.2

From: Benno Schulenberg
Subject: Re: [Help-nano] Segfaults in libc-2.19 w/ 2.9.2
Date: Tue, 16 Jan 2018 21:18:21 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0

Hello Andreas,

[Please answer to the list only.]

Op 15-01-18 om 22:36 schreef Andreas Schamanek:
I love Nano and I am very much excited about several recently added features.

Out of curiosity, which features are those?

Only with 2.9.2, I seem to face segfaults more frequently, yet not very often.

*More* frequently?  You mean older nanos used to crash too, now and then?
If yes, which nanos?  All versions since 2.7.0?

Also not often enough to see a pattern. The 2 most recent segfaults

   Jan 15 22:19:49 wiener kernel: [164886.887031] nano[20676]: segfault
   at ea3fff ip 00007fbe7a4f6ff1 sp 00007fff0ec73948 error 4 in[7fbe7a3be000+1a1000]

   Jan 11 22:58:43 wiener kernel: [9580504.552309] nano[22940]:
   segfault at 15d1fff ip 00007f599578bfdd sp 00007ffe98d64e58 error 4

occurred while typing (no special operations) in 7K large file using syntax highlighting for Markdown,

Nano itself does not come with a syntax file for Markdown.  Please attach
the file that you use for this.  Maybe it contains regexes that trigger the

What can I do to track this down?

Try to recreate the exact situation of the crash as soon as you get a
segfault: open the same file again, type the same stuff again, until
you can reproduce the crash.  Once you can reproduce it, it can be

BTW, there is no auto save feature, is there?

No.  But I have gotten into the habit of pressing ^S now and then.
That key is bound to "savefile" by default since 2.9.0.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]