Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!sran10.sra.co.jp!ishisone
From: ishisone@sran10.sra.co.jp (Makoto Ishisone)
Newsgroups: comp.windows.x
Subject: Re: kinput problem
Message-ID: <9010010949.AA20025@sran10.sra.co.jp>
Date: 1 Oct 90 09:49:35 GMT
References: <1428@quintus.UUCP>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: Software Research Associates, Inc., Japan
Lines: 34

In article <1428@quintus.UUCP>,
Teknowledge.COM!unix!quintus!dimitar@beaver.cs.washington.edu
(Dimitar Bojantchev) writes:
>I am having a problem running kinput on SUN4/110 under OS 4.03.
>It consits of a segmentation fault. Any patches, workarounds?
>
>========== begin session ============
>
>(dbx) run
>Running: kinput
>signal SEGV (segmentation violation) in strcpy at 0xf77034ac
>0xf77034ac:     ld      [%i1], %i3
>(dbx) where
>strcpy() at 0xf77034ac
>js_open() at 0x12518
>useServer() at 0xc550
>jiOpenServer() at 0xd348
> ...

I suspect you don't specify jserver (a kanji-conversion daemon
which kinput uses as conversion engine) hostname in any of resource file,
command-line options and environment variables. Try this:
	% kinput -jserver <hostname-on-which-jserver-is-running>
You can do it by setting environment variable 'JSERVER', too.

This unfriendly action (dumping core) was fixed by kinput fix#1.
There are 3 patches available for kinput, so you should get them and apply.
Patch files are expo.lcs.mit.edu:contrib/R4fixes/kinput/kinput.fix.[123].
You can get them by anonymous ftp.
If you don't have ftp access, please let me know. I'll send by e-mail.

					Makoto Ishisone
					Software Research Associates, Inc.
					ishisone@sra.co.jp