This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--BOUNDARY.139176680.1
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.NEB.4.30.0101091256522.15384@odysseus>

	Testing this under NetBSD/i386 compiling vi with -g to get more
	information yielded:

% setenv TERM amiga-vnc
% gdb /usr/src/usr.bin/vi/build/vi
(gdb) run
Starting program: /usr/src/usr.bin/vi/build/vi

Program received signal SIGSEGV, Segmentation fault.
0x480c3576 in __init_getch ()
(gdb) where
#0  0x480c3576 in __init_getch ()
#1  0x480c30cc in initscr ()
#2  0x804a67c in newterm (a=0x80a60b0 "amiga-vnc", b=0x80a2408,
c=0x80a23b0)
    at /home/netbsd/src/usr.bin/vi/build/../cl/cl_bsd.c:157
#3  0x804c965 in cl_vi_init (sp=0x80a7000)
    at /home/netbsd/src/usr.bin/vi/build/../cl/cl_screen.c:248
#4  0x804c649 in cl_screen (sp=0x80a7000, flags=2)
    at /home/netbsd/src/usr.bin/vi/build/../cl/cl_screen.c:118
#5  0x808aaad in v_init (sp=0x80a7000)
    at /home/netbsd/src/usr.bin/vi/build/../vi/vi.c:928
#6  0x8089227 in vi (spp=0xbfbfda18)
    at /home/netbsd/src/usr.bin/vi/build/../vi/vi.c:90
#7  0x8070475 in editor (gp=0x80a4000, argc=0, argv=0xbfbfdac0)
    at /home/netbsd/src/usr.bin/vi/build/../common/main.c:450
#8  0x804b471 in main (argc=1, argv=0xbfbfdabc)
    at /home/netbsd/src/usr.bin/vi/build/../cl/cl_main.c:117
#9  0x804a435 in ___start ()

	So it looks very clearly that it is blowing up inside curses

	I don't have time to look at this more fully at the moment
	(and I'm also not the curses maintainer which allows the buck
	to pass more easily :)

	Could you use send-pr to report the problem as a bug in the
	curses library, and include your termcap entry and the above
	information, and hopefully the NetBSD curses people will be
	able to look at it soon.

		David/absolute		-- www.netbsd.org: No hype required --


On Mon, 8 Jan 2001, Arto Huusko wrote:

>
> Hi,
>
> I have some trouble with vi. I use (or *would* use) it mostly from a
> telnet terminal in an Amiga ViNCEd console window. I've got an own
> termcap entry for that console driver.
>
> I had no trouble with that (or with vi, anyway) on 1.4.2 but once I
> upgraded to 1.5, vi segfaults on startup. Immediately. Connecting
> with telnet from somewhere else and using other terminals (vt220
> or amiga, for example) fixes everything.
>
> I'm including the termcap entry here, if someone could help...
> The thing I most wonder about, is the fact that everything was so nice
> under 1.4.2.
>
> (The termcap entry was converted and modified by me from a terminfo entry
> supplied by the console driver's author)
>
>

--BOUNDARY.139176680.1
Content-Type: TEXT/PLAIN; NAME=amiga-vnc
Content-ID: <Pine.NEB.4.30.0101091256523.15384@odysseus>
Content-Description: 
Content-Disposition: ATTACHMENT; FILENAME=amiga-vnc

amiga-vnc|Amiga VNC console:\
	:am:da:db:ms:ND:\
	:BT#1:Co#16:co#80:li#50:lm#0:NC#0:pa#256:\
	:bl=^G:mb=\E[7;2m:md=\E[1m:vi=\E[0p:\
	:cl=\E[H\E[J:ve=\E[p\E[>?6l:cr=^M:\
	:cs=\E[%i%d;%dr:LE=\E[%dD:le=\E[D:\
	:DO=\E[%dB:do=\E[B:RI=\E[%dC:nd=\E[C:\
	:cm=\E[%i%d;%dH:UP=\E[%dA:up=\E[A:\
	:vs=\E[>?6h:DC=\E[%dP:dc=\E[P:mh=\E[2m:\
	:DL=\E[%dM:dl=\E[1M:cd=\E[J:ce=\E[K:vb=^G:\
	:IC=\E[%d@:ic=\E[@:AL=\E[%dL:al=\E[1L:sf=\ED:\
	:SF=\E[%dS:mk=\E8m:\
	:is=\E[>?2;18;>?13l\E[>?26;?6;20;>?15;?7;>?8h\E[30;85;>15m\E[ s:\
	:kb=^H:kB=\233Z:kl=\E[D:kd=\E[B:kr=\E[C:\
	:ku=\E[A:kD=\177:k0=\E[9~:k1=\E[0~:k2=\E[1~:\
	:k3=\E[2~:k4=\E[3~:k5=\E[4~:k6=\E[5~:k7=\E[6~:\
	:k8=\E[7~:k9=\E[8~:%1=\E[?~:kh=\E[44~:kH=\E[45~:\
	:Km=\E[M:kN=\E[42~:kP=\E[41~:\
	:oc=\E[30;85;>15m:mr=\E[7m:sr=\EM:SR=\E[%dT:\
	:te=\E[?7h\E[r\E[J:ke=\E[?1l:se=\E[21m:\
	:ue=\E[24m:rs1=\Ec:\
	:r2=\E[>?2;18;>?13l\E[>?26;?6;20;>?15;?7;>?8h\E[30;85;>15m\E[ s:\
	:me=\E[0m:ti=\E[?7h:ks=\E[?1h:so=\E[1m:\
	:us=\E[4m:

--BOUNDARY.139176680.1--