help-nano
[Top][All Lists]
Advanced

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

Re: [Help-nano] Nano crashed when doing a search


From: Stan Horwitz
Subject: Re: [Help-nano] Nano crashed when doing a search
Date: Tue, 4 Sep 2007 15:08:26 -0400


On Sep 4, 2007, at 3:02 PM, David Ramsey wrote:

On 9/4/07, Stan Horwitz <address@hidden> wrote:

<snip>

The machine is a 64-bit server, but it runs Suse 9.

Thanks for the info.  I forgot to ask, though: are you using nano
1.3.x/2.0.x, and what version of glibc does Suse 9 use? Suse's ftp site
doesn't seem to have anything earlier than 9.2 or so.

By the way, sorry if I jumped to conclusions a bit. It's just that this
sounds a lot like the known problem mentioned in the following
links/threads, which wasn't fixed until Suse 10.1 (I don't know if the
fix was backported or not):

http://lists.gnu.org/archive/html/nano-devel/2006-10/msg00011.html
http://bugs.gentoo.org/show_bug.cgi?id=100289

Note that some of the version numbers in the first link are wrong;
you'll have to read through the thread it points to to find out the
right ones.

I will review that thread, but to answer your questions, I am using Nano 2.0.6 ...

Here's what I have for glibc

euler 000/stan# rpm -q --all | grep glibc
glibc-locale-2.3.3-98.73
glibc-devel-32bit-9-200608091927
glibc-i18ndata-2.3.3-98.61
glibc-info-2.3.3-98.61
glibc-locale-32bit-9-200608091927
glibc-devel-2.3.3-98.73
glibc-32bit-9-200608091943
glibc-2.3.3-98.73



--
Stan Horwitz
Temple University
Enterprise Systems Group
address@hidden

CONFIDENTIALITY STATEMENT: The information contained in this e-mail, including attachments, is the confidential information of, and/or is the property of, Temple University. The information is intended for use solely by the individual or entity named in the e-mail. If you are not an intended recipient or you received this in error, then any review, printing, copying, or distribution of any such information is prohibited. Please notify the sender immediately by reply e-mail and then delete this e-mail from your system.






reply via email to

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