Re: vim-6.0 crashed SIGBUS in clear_termcodes() / ncurses

[Thomas Dickey]

On Fri, Jan 18, 2002 at 09:32:13AM -0800, Lawrence Carver wrote:
> Hi, I've been able to use vim-6.0 on many Solaris 2.x systems,
> without any real problem.  But on my Sun UE4500, running SunOS
> 5.7, I was having a hard time getting it to start up.
> 
> I'd tried building vim-6.0, with or without available source
> patches, using gcc-2.95.3, or Sun's SUNWspro v5, or Forte 6.2,
> and at runtime (or if I test "./src/vim"), it always crashed
> on startup, like so -->
> 
>   Running: vim 
>   (process id 1072)
>   signal BUS (invalid address alignment) in clear_termcodes \
>              at line 3415 in file "term.c"
> 
>   3415       ospeed = 0;

well ospeed is a short.  There are some downstream mods that made it a long,
but I've disowned those.  That could be the problem.

>   (/opt/SUNWspro/v6.2/bin/../WS6U2/bin/sparcv9/dbx) where 100
>   =>[1] clear_termcodes(), line 3415 in "term.c"
>     [2] clear_termoptions(), line 6917 in "option.c"
>     [3] set_termname(term = 0x1cd7b8 "xterm"), line 1774 in "term.c"
>     [4] termcapinit(name = (nil)), line 2447 in "term.c"
>     [5] main(argc = 0, argv = 0xffbef560), line 1104 in "main.c"
> 
> 
> I'd tried different term types (using "-T xxx"), but it crashed
> in the same way.  *** At the same time, I could build and run
> vim-5.8 on this system, any time, and it would run just fine.
> 
> Then, before complaining too loudly I went back and tried re-
> making my ncurses-5.2 (again;) ... forcing it to build using
> Forte 6.2, instead of gcc-2.95.3 (it didn't seem to want to,
> until I fooled configure;).

for example?  (I recall adding some fixes for the c++ binding, but nothing
that should affect ncurses' configure script).

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net