X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f Date: Sat, 26 Jan 2002 09:40:40 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: djgpp AT delorie DOT com Message-Id: <1190-Sat26Jan2002094040+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: juhas AT blue DOT seas DOT upenn DOT edu (PAVOL JUHAS) In-reply-to: (juhas@blue.seas.upenn.edu) Subject: Re: vim (dos32) hangs under djgpp bash References: Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: juhas AT blue DOT seas DOT upenn DOT edu (PAVOL JUHAS) > Newsgroups: comp.editors,comp.os.msdos.djgpp > Date: 25 Jan 2002 21:52:09 GMT > > Martin Stromberg (eplmst AT lu DOT erisoft DOT se) wrote: > > PAVOL JUHAS (juhas AT blue DOT seas DOT upenn DOT edu) wrote: > > : I have a frequent problems with Win98 getting frozen, when using vim > > : (version 6.0 for dos32 djgpp) under djgpp2.03 bash (ver.2.04.7). The > > : system gets completely non-responding and the only way out is to restart > > : the computer. > > I am not sure if this is a bug in vim, bash or most likely windows. > However the crashes occur when I use djgpp vim with djgpp bash. Say, I > have a junk.bat file of 10 "vim -c q" lines. If I run it under > command.com, it works, but "source junk.bat" in djgpp bash would freeze > the system. This rings a bell. Could you please try the following experiment: invoke vim from COMMAND.COM, but via Make, like this: c:\> make -f - all: vim -c q vim -c q vim -c q ^Z Every line after "all:" should begin with a TAB. The "^Z" at the end is the Ctrl-Z character: it ends the Makefile and starts the Make run. (It doesn't really matter what commands are in the `all:' rule, as long as they are similar to those which cause the system to freeze when you invoke vim from Bash. Also, I only put several identical lines in the above bacause you seemed to indicate that was a good way of reproducing the problem; if a single command is enough, please use just that single command.) The idea here is to see whether vim freezes when invoked from _any_ DJGPP program, or just from Bash. You could also try other DJGPP programs which can invoke arbitrary programs, like Less or Info. If invocation from other DJGPP programs also cause the freezes, then the problem is likely to be the one described in section 6.1 of the DJGPP FAQ list: on some Windows systems, calling some functions of interrupt 2Fh has such a nasty effect, probably due to a bug in one of the Windows components. (The FAQ talks about function 1680h, but the problem is not limited to that function alone.) So you could ask the vim developers to check whether the DJGPP port either uses the library function __dpmi_yield, or invokes some other function of Int 2Fh via int86 (as opposed to __dpmi_int). If it does, this could be the cause of your problems.