lee@minnow.UUCP (09/01/87)
I have found some bugs microp, I think, that no one else has posted.
If I am wrong please let me know where my error is. *note* all of these
occured while running under csh, I haven't verified there failure under sh.
1. setting a "cdpath" in the csh doesn't work at all. You can set the variable but the cd command doesn't honor it.
2. With my ega monitor; if I set a "bright" forground color and then run a
program which uses curses, the forground color is change to the cooresponding
"darker" color.
3. If you run the "crash" program and type mount (to display the mount
table) crash will crash (core dump).
4. The .exrc file (used by vi) should be placed in the home directory. Under
microport (alias macrobug), if this file is not in the current directory it
is not used by the editor. (this is a real pain in the a__ since you have
to have a copy of .exrc in every directory you edit in)
5. I have a fifteen line program that does nothing but a floating point
multiply in a continues loop and displays the result using curses. After
a time(seems random) the program gets a floating point error and terminates
with a core dump. Using sdb to read the core file; it says the program
died in ecvt.c (THEIR math library). What makes this problem strange is
that if I elimate the curses display from this program (leaving even less
than fifteen lines) the program seems to run forever. WHAT DOES CURSES HAVE
TO DO WITH FLOATING POINT???
If anyone else can verify these problems I would like to hear about it. If
I'm wrong about any of these I would also like to hear about that too.
Gene W. Lee
Gene Lee UUCP: ...ihnp4!{meccts,dayton,rosevax}!ems!minnow!lee
UNISYS Corporation ATT: (612) 635-6334
If not for the courage of the fearless manager, the paycheck would be lost.
--
Gene Lee UUCP: ...ihnp4!{meccts,dayton,rosevax}!ems!minnow!lee
UNISYS Corporation ATT: (612) 635-6334
If not for the courage of the fearless manager, the paycheck would be lost.peter@sugar.UUCP (Peter da Silva) (09/04/87)
> 4. The .exrc file (used by vi) should be placed in the home directory. Under > microport (alias macrobug), if this file is not in the current directory it > is not used by the editor. (this is a real pain in the a__ since you have > to have a copy of .exrc in every directory you edit in) Some Unixes have this "feature". The solution is to setenv EXINIT "so $HOME/.exinit" And then move your .exrc to .exinit. The logic behind this feature, by the way, is that you can have a seperate .exrc with different macros in different places. -- -- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter -- U <--- not a copyrighted cartoon :->