[Top][All Lists]

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

Re: [Nano-devel] 1.3.7 core dump

From: Nick Warne
Subject: Re: [Nano-devel] 1.3.7 core dump
Date: Thu, 30 Jun 2005 17:36:44 +0100
User-agent: KMail/1.8.1

Hi All,

>> If I then start nano, load a file, then goto a line number using
>> Ctrl+Shift _ [type] # it will core dump.
>> I could replicate this ever time with any file. 

On Wednesday 29 June 2005 17:40, David Lawrence Ramsey wrote:
> This is very odd.  I've only had two kinds of segfaults with nano
> recently: (a) in display_string() due to a potential buffer overrun
> (fixed in 1.3.7 by the attached patch), and (b) in _nc_screen_wrap()
> inside ncurses 5.4 (which only seems to occur in UTF-8 mode).
> 1. Does the attached patch change anything?
> 2. If not, could you provide a gdb backtrace using the core file, so I
> can see where nano's crashing?
> 3. Does this also happen with 1.3.8-cvs?
> Thanks in advance.

Well, this is even weirder, and I have never experienced anything like this 

I wanted to get a gdb debug on this today before patching, so rebuilt nano 
1.3.7 without the --disable-utf8.  It all worked perfectly (segfault before).

So I then rebuilt 1.2.5 and installed that, seeing if it overwrote some 
install files - then created a new 1.3.7 src tree and rebuilt again.  I did 
this several times with different variations - and NOT once can I replicate 
the segfault I was getting _everytime_ as I stated.

I will watch this... but it appears nothing is wrong now?


"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."

reply via email to

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