jdh@aragorn.UUCP (jim harriger) (04/20/88)
if there is anybody out there running GNU emacs on System V.3/386,
i could use your help.
i brought up GNU emacs 18.50 on UNIX(r) V.3/386 about two weeks ago.
since then, i have noticed two problems which i'm hoping someone out there
can help me solve. If it helps, i was running 18.42 before this and didn't
have either one of these problems.
1) frequently, when doing filename completion in the minibuf, emacs
will freak-out on me. it repeatedly prints "Modification-flag cleared"
in the minibuf, beeping all the time, finally gives that up, and
completes my filename with the string 'BOo . It then refuses
to read anything more from the keyboard, and is in a loop in
user code (meaning it is not sleeping and it is not looping in
the kernel somewhere.) i can kill it with a kill from another
terminal, and then the tty line is left in raw mode.
2) if i do a lot of filename completion operations that require emacs to
open a directory and print me a list of the possible filenames,
after some time, emacs runs out of file descriptors, and cannot
open any more files. looking at the user structure with crash shows
6-8 open files.
anybody have any ideas? anybody else see this? maybe it is related to
my configuration or something.
relevant data: UNIX V, Release 3.0, running on an 80386-based Multibus I
box. has 8Mb RAM, 500Mb disk space, GNU emacs 18.50
btw, i'd like to thank whoever it was out there who finally made unexec
work on UNIX V.3/386. thanks, whoever you are!
--
______________________________________________________________________________
intelcs! ----\ | Jim Harriger
tektronix!reed! -----> littlei!jdh | Oregon Systems Division, Intel Corp.
ogcvax! ----/ | Hillsboro, ORmdc@mcp.entity.com (Marty Connor) (04/21/88)
In article <201@aragorn.UUCP>, jdh@aragorn.UUCP (jim harriger) writes: > if there is anybody out there running GNU emacs on System V.3/386, > i could use your help. > 1) frequently, when doing filename completion in the minibuf, emacs > will freak-out on me. it repeatedly prints "Modification-flag cleared" We had some troubles like this when we first compiled it; It would seem to have something to do with the optimizer, because the problem when away when we re-compiled without the -O option. This is of course not the best answer, but may get the behaviour you desire. > 2) if i do a lot of filename completion operations that require emacs to > open a directory and print me a list of the possible filenames, > after some time, emacs runs out of file descriptors, and cannot > open any more files. looking at the user structure with crash shows > 6-8 open files. This one I didn't notice; try removing "-O" from your options if you're using it and re-compile the whole thing. > btw, i'd like to thank whoever it was out there who finally made unexec > work on UNIX V.3/386. thanks, whoever you are! Gary Byers (gb@entity.com) did our unexec for SCO Xenix 386. It was included with release 18.50 with some minor changes. Hope this helps you get going. I am composing this message on a Wyse 386 box running SCO Xenix 2.2.1. -- ---------------- Marty Connor Director of Innovation, The Entity mdc@mcp.entity.com, ...{harvard|uunet}!mit-eddie!spt!mcp!mdc
dougm@ico.ISC.COM (Doug McCallum) (04/21/88)
In article <201@aragorn.UUCP> jdh@aragorn.UUCP (jim harriger) writes: > > 1) frequently, when doing filename completion in the minibuf, emacs > will freak-out on me. it repeatedly prints "Modification-flag cleared" Don't know about this one, but it may be related to the next one. > 2) if i do a lot of filename completion operations that require emacs to > open a directory and print me a list of the possible filenames, You are probably useing the V.3 opendir/readdir/closedir calls with the GNU malloc routines. This will cause the symptoms of your second problem. closedir does a free on the data structure BEFORE it closes the file descriptor. The GNU malloc scribbles on the file descriptor field during the free. The close never happens.