Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!agate!shelby!polya!modesty!ramani From: ramani@modesty.Stanford.EDU (Ramani Pichumani) Newsgroups: comp.windows.x Subject: Re: DEC widgets on System V Message-ID: <11509@polya.Stanford.EDU> Date: 24 Aug 89 09:15:52 GMT References: <10045@phoenix.Princeton.EDU> Sender: USENET News System Reply-To: ramani@modesty.Stanford.EDU (Ramani Pichumani) Organization: Stanford University Computer Science Department Lines: 46 > With these (System V) flags defined I can get it to compile, but > when I try to execute the test programs it core dumps. Sadly, it > does not core dump in the DEC code, it core dumps in XtInitialize. This is not a answer to your question but rather an expansion of the problem. We have recently compiled GNU emacs 18.53 on our 4D with the X windows options. The compilation and linking worked fine but when the code executes, it too bombs out. However, I can also run xemacs remotely from my Sun 3 and Sun 4 without any problems. This leads me to suspect either a bug in the GNU code (which is only specific to SGI) or a problem in Xlib. I have included the stack frame from the core file at the end of this message. The problem seems to be somewhere in XOpenDisplay. Fatal error(11). segmentation violation. 0 kill.kill(0x1045034, 0x0, 0xb, 0x0, 0x7fffcae0, 0x4812d0) ["kill.s":17, 0x482fd4] 1 fatal_error_signal(sig = 11) ["emacs.c":143, 0x4192a4] 2 index.index(0x10027fa4, 0x1002d6f0, 0x0, 0x0, 0x7fffcae0, 0x0) [0x46542c] 3 res_init.res_init(0x0, 0x0, 0x0, 0x0, 0x0, 0x0) ["res_init.c":117, 0x462980] 4 res_search(0x0, 0x0, 0x0, 0x0, 0x400, 0x0) ["res_query.c":131, 0x462cfc] 5 _gethostbyname_named(0x7fffc238, 0x477390, 0x0, 0x0, 0x0, 0x4773e8) ["gethostnam.c":235, 0x46143c] 6 gethostbyname(0x2, 0x0, 0x0, 0x0, 0x0, 0x0) ["gethostwrap.c":18, 0x460d9c] 7 _XConnectDisplay(0x7fffcae0, 0x7fffc56c, 0x7fffc46c, 0x7fffc468, 0x7fffc43c, 0x7fffc438) ["XConnDis.c":276, 0x4773e4] 8 XOpenDisplay(0x0, 0x0, 0x0, 0x43a908, 0x0, 0x0) ["XOpenDis.c":166, 0x46f6e8] 9 x_term_init() ["x11term.c":1520, 0x415594] 10 .block4 ["dispnew.c":1405, 0x4032e8] 11 init_display() ["dispnew.c":1405, 0x4032e8] 12 main(argc = 1, argv = 0x7fffc774, envp = 0x7fffc77c) ["emacs.c":362, 0x419730] I don't know if this problem is related to the one posed above but I sure would like to know if anyone has gotten xemacs working on release 3.1G. Ramani Pichumani E-mail: ramani@na-net.stanford.edu Department of Computer Science, Margaret Jacks Hall, Room 308, Stanford University, Stanford, CA 94305 USA