delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/02/23/14:48:28

From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <199902231947.UAA09421@father.ludd.luth.se>
Subject: Re: emacs hangs my machine
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Tue, 23 Feb 1999 20:47:57 +0100 (MET)
Cc: djgpp AT delorie DOT com (DJGPP)
In-Reply-To: <199902230907.KAA04844@juno.erisoft.se> from Martin Stromberg at "Feb 23, 99 10:07:49 am"
X-Mailer: ELM [version 2.4ME+ PL15 (25)]
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com

According to Eli:
> On 22 Feb 1999, Martin Stromberg wrote:
> 
> > WINDOZE 4.1 (98), open DOZE box, run emacs, "C-x C-f e:/a/1 RET" (read in 
> > the file e:/a/1) which is 1MB, "C- " (set mark), "M->" (goto end), "C-w" 
> > (kill-region). Now the cursor changes to a timeglass and the machine is 
> > completely stuck. Not even C-Alt-Del works.
> 
> Does this happen with "emacs -q" as well?  If not, look in your _emacs
> for the reason(s).

Yes.

> If "emacs -q" doesn't help, try this:
> 
> 	  emacs -q
> 	  M-: (setq x-select-enable-clipboard nil) RET
> 
> and then do the same sequence you described above.  Does this solve
> the problem?

Yes.

> If it does, the problem is with copying the killed text into the
> Windows clipboard.  1MB is too large for this (copying is done through
> conventional memory), but Emacs should have noticed that and should
> have printed a message that the text is too large to be put into the
> clipboard.  This diagnostics is based on the assumption that trying to
> allocate a buffer that is too large returns an error from __dpmi_int.
> It is possible that kills larger than 1MB cause a wrap-around in 20
> bits of DOS address space, so Windows allocates a much smaller buffer
> and ``succeeds'', and Emacs then cheerfully writes over some system
> memory.  Try killing less than 1MB, say, 900KB, and see if it still
> hangs.

Ok. A crash dump (over the text) is the result and the box heading
says "Finished - emacs"

> What kind of data was in that file?  Is it text or binary (including
> null characters)?  Binary data could make all kinds of trouble when
> you put it into the clipboard, and Emacs 19.34 on SimTel doesn't
> do anything to prevent binary data from being put into the clipboard.

Text data, but rubbish (for testing purposes).

Hmm. I'll exchange the rubbish characters with spaces. See crash
backtrace last.

> > Sometimes, after "C-w", the DOZE box's screen is corrupted.
> 
> With that same 1MB of killed text, or with other files and smaller
> kills as well?

Same file. It depends on the settings of the DOZE box, I think.


Right,

							MartinS

Emacs aborted!
Exiting due to signal SIGINT
Control-Break Pressed at eip=0007acdf
eax=00020008 ebx=00d700af ecx=00000000 edx=00000fff esi=0000000e edi=0012a000
ebp=00220698 esp=00220670 program=F:\DJGPP\GNU\EMACS\BIN\EMACS.EXE
cs: sel=00a7  base=83d63000  limit=0051ffff
ds: sel=00af  base=83d63000  limit=0051ffff
es: sel=00af  base=83d63000  limit=0051ffff
fs: sel=00d7  base=00000000  limit=ffffffff
gs: sel=00d7  base=00000000  limit=ffffffff
ss: sel=00af  base=83d63000  limit=0051ffff

Call frame traceback EIPs:
  0x0007acdf
  0x00057407
  0x0001a1c6
  0x00009483
  0x000087e9
  0x00008912
  0x000091db
  0x00003c8d
  0x0007507c
  0x00058ef1
  0x0006bc92

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019