Re: [gentoo-dev] Why not vi?

[wes chow <wes@woahnelly.net>]

> > When I  discovered, to my surprise, that  I was forced to  use nano, I
> > immediately decided to take your  Portage system for a spin, and typed
> > 'emerge  app-editors/vi'.  Vi was  built from  source (though  I'm not
> > clear on which particular vi you  used).  However, when I tried to run
> > it, it segfaulted.  So I was stuck with nano.
>
> Could you please give me a backtrace of this?  I'm the one "responsible"
> for vi as of the moment, and this is the second occurance of a random
> heisenbug for vi that I've seen, noone so far has been able to debug it
> since it goes away with their second install (It works for me, in the
> systems I've tried, could be a library interdependency bug)

It segfaults for me too... but only if I run vi in the plain text console
(please correct me if I use the wrong terminology -- I'm new to Linux, but
not to Unix).  If I run vi from withing Gnome, it works fine.  I have yet
to install it a second time.

The backtrace doesn't look so instructive since there's no debug
information in the executable (and I'm afraid that recompiling vi will
make the problem go away):

#0  0x400495aa in tgoto () from /lib/libncurses.so.5
#1  0x0805856a in getline ()
#2  0x08049fad in strcpy ()
#3  0x4007e3bd in __libc_start_main () from /lib/libc.so.6

Is there anything you need to know about my system?


Wes