Re: Segfaults in libc-2.19 w/ 2.9.2

Op 17-01-18 om 00:12 schreef Andreas Schamanek:
> Seriously, I cannot remember any crashes since 2.6 or 2.7

Sounds good.  :)

In your markdown.nanorc I cannot find anything suspicious.
There seem to be some superfluous backslashes in there, but
they shouldn't cause any problem.  Although... who knows?

For example, in this line:

     color green "\*[^\* ]\*"

The [^\* ] means "anything except backslash and star and space".
But is that backslash excluded on purpose?  Or is it meant to
rob the star from its specialness?  (The latter is unneeded
between square brackets.)

>>> What can I do to track this down?

How do you compile your nano?  With what configure options?
Please show the output of 'nano --version'.

And what CFLAGS do you use?  'echo $CFLAGS'

If a crash happens again, you will want it to be with a nano
that has debugging symbols included.  So your CFLAGS should
contain '-g'.

Even better, Brand Huntsman has posted a patch that should
produce a backtrace automatically whenever nano would crash:

   http://lists.gnu.org/archive/html/nano-devel/2018-01/msg00064.html

However, after applying the patch, nano fails to compiler for me.
But... maybe in a few days Brand will post a version that does work.
It may pay off to keep an eye on that.

Benno