Mail Archives: djgpp/1997/01/16/02:11:29
On Wed, 15 Jan 1997, Paul Loewenstein wrote:
> In my path was still the original path to emacs 19.30; I speculate
> that I inserted the c:/gc/gnu/emacs/bin AFTER the emacs 19.30 path. I
> further speculate that as a result emacs 19.34 was executing some
> emacs 19.30 images.
While the general idea of such a conflict seems the most probable cause
for your trouble, I don't get the specifics. In particular, Emacs
doesn't run any ``images'' at all, it only loads some byte-compiled ELisp
code. There are 2 explanations to the crashes that I can think of:
1) Somehow, the stub of Emacs 19.34 was erroneously loading the COFF
program from Emacs 19.30. AFAIK, this is generally impossible, as the
stub opens and reads the pathname it finds in its argv[0], but I might
miss some problem (or bug) which are triggered by your installation.
2) Emacs 19.34 loaded ELisp startup files which belong to Emacs
19.30 and crashed due to incompatibilities between the versions. This
also shouldn't happen, as Emacs computes the place of the lisp directory
using its argv[0], it doesn't depend on the value of PATH.
> How does emacs 19.34 look for images that it needs to run? Does it
> include either the directory current when it was started or the
> directory in which emacs.exe resides, in its search? If the above
> argument is valid, then it doesn't search first in these directories.
It usually uses argv[0], as I described, but there are complications
which might lead to a different directory, especially in cases like yours
which invite conflicts.
> It is interesting to note that when I run DOS4GW version of
> Ghostscript, I end up with a massive memory leak only fixed by
> shutting down and restarting DragonDictate, whereas with djgpp
> v2 compiled Ghostscript, everything appears fine.
CWSDPMI is not fully compatible with DOS4GW. In fact, on my machine,
Ghostscript/DOS4GW crashes when run by Emacs, if I use CWSDPMI as the
DPMI host.
- Raw text -