Mail Archives: djgpp/1998/06/25/13:30:54
On 25 Jun 1998, Ian Miller wrote:
> I use the term "nukes the DOS box" to mean that it wipes the DOS box from
> the system. To paraphrase Monty Python, it is an ex DOS box, it is no more.
> So taking a snapshot of the screen is not a possibility.
I think if you uncheck the "close on exit" option in the property sheets
of the DOS box, it doesn't close when the program exits, and you get the
chance to copy the screen snapshot into the clipboard. And if Windows
detects some problem with the DOS box, it usually pops up a dialog box
saying "This application performed an illegal operation... etc.". Did
that happen for you?
Can you at least tell where exactly in the dumping process does it
happen? Did it load all the Lisp files and wrote "Dumping under the name
emacs" before it blew up? I need some starting point, so please help me.
> I suspect that this is something to do with DPMI and the sheer size of the
> emacs executable(s).
If there's a problem with memory, it should just say so. But temacs
doesn't consume a lot of memory anyway when it runs in batch mode.
> Perhaps the temacs.exe stubify command is not
> working correctly...
If you mean the the small stack size, you can increase it and see if that
helps.
Another thing to test is to type "temacs -l loadup" from the DOS prompt
in the Emacs src directory, and see if temacs.exe comes up and works.
Btw, what version of binutils do you use? Did you use the same version
with both gcc 2.8.1 and 2.7.2.1?
> I'd be investigating
> this more actively if there were not lots of *really important* World Cup
> football matches on at the moment :-)
Emacs 20.3 is about to be released, so it'd be swell if it would compile
with 2.8.1 as well. As you understand, I cannot debug a problem that I
don't see.
- Raw text -