SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It is the same for both of you? Do you have a standard and full Slackware installation? I have a, ap, d, l, n, x installed completely.
If I force a core dump and then look at this with gdb I get:
Reading symbols from /tmp/nedit-5.5-Linux-x86/nedit...(no debugging symbols found)...done.
[New LWP 11516]
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
Core was generated by `nedit'.
Program terminated with signal 11, Segmentation fault.
#0 0xb73f8108 in __overflow () from /lib/libc.so.6
How can I find out exactly where its crashing; I suspect it is in some X related
lib; what else can I try?
perseus12: I see my initial guess that the problem relates to UTF8 was probably wrong. I have changed my UTF8 locale settings to the stock ones (i.e., those you are using) but nedit still crashes. But, contrary to your case, it starts fine with "env LANG=C nedit".
I have stock Slackware-14.0 installation with a few libraries and programs added but none of them is used by nedit, as far as I can judge. "ldd nedit" shows exactly the same list of libraries as you listed.
Actually, I am a bit lost. I used to run nedit in Slack-13.37 with the en_US locale, and it worked fine. Will let you know if I have an idea.
Nedit has always been my preferred text editor (and it still is). Regarding your question, the results of both 'locale' and 'ldd' are just like yours (above). Hence, there seems to be nothing wrong with the binaries nor the environment. On the other hand, the error of the core dump referring linux-gate.so.1 (see http://www.trilithium.com/johan/2005/08/linux-gate/) reminded me of something related with a VDSO parameter in the kernel. This is a long shot, but might be worth trying. Nowadays, in my 3.6 Kernel configuration I have "Processor type and features"--->"Compat VDSO support" set to N (none), but I recall a time where setting this to N would break a lot of things, especially if "old" software was involved. The kernel help says:
│ Map the 32-bit VDSO to the predictable old-style address too. │
│ Say N here if you are running a sufficiently recent glibc │
│ version (2.3.3 or later), to remove the high-mapped │
│ VDSO mapping and to exclusively use the randomized VDSO. │
│ If unsure, say Y. │
You may try enabling or disabling it, depending on its default state.
Yes nedit has always been my preferred ed as well, although because of the recent problem with nedit I discovered 'geany' and I like it very much for python programming.
As to your suggestion: I don't know what Slackware's stock kernels use but I have always had VDSO=y because that was the default (now running 3.2.33) and nedit was OK. You may be right about vdso, however I now
think that the culprit is 'lesstif' (perhaps + vdso), because keeping everything the same, if I use lesstif nedit crashes, if I use openmotif nedit works better than it has ever worked. What I mean by that is it responds faster now and a big irritation is gone: the open file dialog has two panel areas: left = select directory and the right for selecting files. With lesstif the right area was always tiny so I have to constantly expand it manually, but with openmotif the fileopen dialog adjusts itself to the size of longest dir name AND file name.
I should have switched to openmotif years ago :-) If you feel like it, give openmotif a try and let us know your findings.