Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!cs.utexas.edu!uunet!mcsun!chsun!hslrswi!aut!nbladt From: nbladt@autelca.ascom.ch (Norbert Bladt) Subject: Re: XView - how much of it is available? Message-ID: <1992Nov16.125013.23135@autelca.ascom.ch> Organization: Ascom Autelca AG, Guemligen, Switzerland References: <1992Nov10.172651.23663@Urmel.Informatik.RWTH-Aachen.DE> <1992Nov11.152527.18329@tinman.mke.ab.com> Date: Mon, 16 Nov 1992 12:50:13 GMT Lines: 61 tdphette@mke.ab.com (Thad Phetteplace x4461) writes: >kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: [questions about XView and availability for 386BSD deleted - NB] >I managed to port the props program (executed by the Properties menu >selection) a few weeks ago. I'm currently working on the termsw bug >(suggestions welcome). I'll put the modified props source code and >executable on my ftp server tinman.mke.ab.com sometime tommorow. It >will be in the /pub/386bsd/ports directory. I will put my ported >version of pcomm in there as well. I will make an attempt at >compiling xlock tonight and if that works I will finish porting >Xlockup. Hello everybody ! Yesterday I managed to get the xview client textedit to run without a crash ! It seems to me that the bug you are looking for is not in the textsw part of the xview library. In fact, there seems to be a bug in the optimization of the GNU C-compiler included in the stock-386BSD, I think. What I did to get textedit to run without a crash was: I undefined #OS_HAS_LOCALE (after a suggestion from the net). I compiled all the stuff, yes, the whole libxview.a with the "-g" option to be able to debug it with the wonderful X-debugger "ups" (thanks for this very nice and useful application whoever did it). Imagine what happened, after I finished linking the textedit.o file (compiled with "-g", too) and the libraries. I started "ups textedit" for debugging textedit. I loaded a file into textedit (that's where it crashed before) and it didn't crash this time !! So, I thought, nothing new for me. I did see several applications run fine with a debugger but not without it. So, I started textedit from the commandline. Again, no crash while loading a file. I didn't test it a lot, but it seems to work for me. I will try to compile the whole libxview.a library with "-O" flag except the textsw (and perhaps the ttysw) part of it. The "ups" debugger reported a "segmentation violation" in one of the textsw functions in the version of the libxview.a compiled without "-g". That's what I found out before I compiled all the stuff with "-g" (which will disable optimization). Oh yes, I am still using the gcc which was included in stock-386BSD. I just have gcc 2.2.2 but didn't spend any time on porting it (or applying the patches for 386bsd and just compile it) because now we have gcc 2.3.1 and I will use that, anyway. One thing is still bad. Trying to link "cmdtool" with the large (about 18MB) libxview.a resulted in ld: got signal 10 (or something like this). I have to work on this, too, I guess. That's a report of my intermediate result. Hope this saves somebody else at least some time. Norbert. -- Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland Phone: +41 31 999 65 52 FAX: +41 31 999 65 44 Mail: nbladt@autelca.ascom.ch UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt