[Top][All Lists]

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

Re: [Nano-devel] solving a history bug in nano [patch]

From: Tito
Subject: Re: [Nano-devel] solving a history bug in nano [patch]
Date: Mon, 30 May 2016 14:23:56 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0

On 05/30/2016 09:20 AM, Benno Schulenberg wrote:

On Sun, May 29, 2016, at 23:58, Tito wrote:
if i run it with valgrind it does not segfault and there is nothing
suspicious in the TRAIL file, without valgrind it segfaults at first

Okay.  First try running 'src/nano --ignore', to exclude the possible
influence of any settings and of unexpected characters in the exsisting
history file.

Done, segfaults.

  If that still segfaults, then try instead of (size_t)-1
the values 100, 255, 32000, 65535.  If none of those segfault, then at
least we have a workaround: nobody is going to type sixty-five thousand
characters to search for.

Had time to test only with 65535 and it works (search and previous next search history)

Put back (size_t)-1 and then run 'gdb src/nano', type 'run', make it
segfault, and then type 'backtrace'.



reply via email to

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