[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs 22.1.50 death on 64-bit Windows

From: Kevin Layer
Subject: Re: emacs 22.1.50 death on 64-bit Windows
Date: Tue, 22 May 2007 07:39:27 -0700

Eli Zaretskii <eliz@gnu.org> wrote:

>> > Date: Mon, 21 May 2007 16:11:01 -0700
>> > From: Kevin Layer <layer@franz.com>
>> > 
>> > Start up the 32-bit version of emacs (I know of no 64-bit version)
>> > with -q and eval this in *scratch*:
>> > 
>> >    (start-process "foo" "*foo*" "c:/windows/notepad.exe")
>> > 
>> > and your emacs will disappear after a couple of seconds.
>> Problems in CVS versions of Emacs are better reported to
>> emacs-devel@gnu.org, not here.  This list is for released versions of
>> Emacs.

It happens in currently release versions, too.

>> > Ideas for debugging?
>> First, can you try the latest pretest of Emacs 22.1?  You can find it
>> here:
>>   ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-22.0.990.tar.gz

I will download and test this today.

I assume this is a source and not binary distribution.  Is is supposed
to build on 64-bit Windows, or do I do the "build on 32-bit and run on
64-bit" thing?

I also wonder how the above differs from what's in CVS.  I checked my
version out of CVS yesterday.

>> It is more important now to fix bugs in the pretest because we expect
>> to release v22.1 very soon.  By contrast, v22.1.50 is the development
>> version that will not be released for at least a few months.
>> If the above pretest also crashes on 64-bit Windows, the best way to
>> debug this is to run Emacs under a debugger (GDB if your Emacs was
>> compiled with GCC or Visual Studio if it was compiled by MSVC).

Yes, I know that's the best way, but it does require knowledge of
emacs internals that I do not possess.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]