nano-devel
[Top][All Lists]
Advanced

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

Re: [Nano-devel] Crash report - segfault reproduceable


From: David Lawrence Ramsey
Subject: Re: [Nano-devel] Crash report - segfault reproduceable
Date: Thu, 02 Feb 2006 18:02:40 -0500
User-agent: Thunderbird 1.5 (X11/20051201)

Nick Warne wrote:
> On Tuesday 31 January 2006 00:05, Mike Frysinger wrote:
>> i found that i could also reproduce this in Windows by logging in
>> with putty, exporting TERM=putty, and then resizing the terminal
>> -mike
>
> Well I can get this to segfault easy now, even on opening the test
> file if I do not resize the window when it does segfault - if you need
> to run some debug code to trace, I am willing to help.
>
> I have looked at the code, but I think you need to be a nano veteran
> to follow it - it's a bit awkward to follow for a virgin...

No problem.  Would you try getting the latest CVS, applying the
following patch, running nano WITHOUT the -O/--morespace option (as the
debugging output is on the line that that option makes part of the edit
window) so that it crashes, and telling me what results are shown during
the entire session?  Thanks in advance.

diff -ur nano/src/winio.c nano-fixed/src/winio.c
--- nano/src/winio.c    2006-01-30 16:23:51.000000000 -0500
+++ nano-fixed/src/winio.c      2006-02-02 17:55:41.000000000 -0500
@@ -1922,6 +1922,10 @@
 
     free(buf_mb);
 
+    mvwprintw(topwin, 1, 0, "line %ld: allocated %lu bytes, index == %lu, 
converted length == %lu\n",
+       (openfile == NULL) ? -1 : (long)openfile->current->lineno, (unsigned 
long)(alloc_len + 1), (unsigned long)index, (unsigned long)(strlen(converted) + 
1));
+    wrefresh(topwin);
+
     if (index < alloc_len - 1)
        converted[index] = '\0';
 

reply via email to

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