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

[Tito]

On 05/29/2016 10:25 PM, Benno Schulenberg wrote:
> 
> On Sun, May 29, 2016, at 21:58, Tito wrote:
>> after a lot of fiddling this are my results, nano 2.5.3:
>> 1) original source: search history does not work but nano works
>> 2) with your patch: as soon as you do a search nano segfaults,
>>
>>      ^W ahahaha <Enter>  boom
> 
> :|
> 
>> Ideas about how to debug it even If I don't
>> use the N900 nowadays I would like to fix
>> it.
> 
> Run 'valgrind --leak-check=full --track-origins=yes src/nano 2>TRAIL',
> search for something, and after it segfaulted look at the TRAIL file.
> Or if it does not segfault, just exit nano after the search, and look
> at the TRAIL file.
> 
> Benno
> 
Hi,
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
search.

:-/

Ciao,
Tito
Nokia-N900:~# valgrind --leak-check=full --track-origins=yes ./nano 2>TRAIL
Nokia-N900:~# cat TRAIL
==2079== Memcheck, a memory error detector
==2079== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==2079== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info
==2079== Command: ./nano
==2079==
==2079==
==2079== HEAP SUMMARY:
==2079==     in use at exit: 509,391 bytes in 663 blocks
==2079==   total heap usage: 1,216 allocs, 553 frees, 577,477 bytes allocated
==2079==
==2079== LEAK SUMMARY:
==2079==    definitely lost: 0 bytes in 0 blocks
==2079==    indirectly lost: 0 bytes in 0 blocks
==2079==      possibly lost: 0 bytes in 0 blocks
==2079==    still reachable: 509,391 bytes in 663 blocks
==2079==         suppressed: 0 bytes in 0 blocks
==2079== Reachable blocks (those to which a pointer was found) are not shown.
==2079== To see them, rerun with: --leak-check=full --show-reachable=yes
==2079==
==2079== For counts of detected and suppressed errors, rerun with: -v
==2079== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 19 from 8)