[Top][All Lists]

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

Re: Abort when creating frame

From: Eli Zaretskii
Subject: Re: Abort when creating frame
Date: Tue, 06 Sep 2011 19:57:18 +0300

> Date: Tue, 06 Sep 2011 14:23:29 +0200
> From: martin rudalics <address@hidden>
> Cc: address@hidden
> I now know what happens but don't understand why.  I'm running the
> debugger from an older emacs and `insert-file-contents' loads
> uni-mirrored.el from the directory of _that_ emacs.  This also
> explains why I see the abort only when running under gdb.  If I run
> gdb from the new emacs, the debugged emacs starts as expected.

This is a feature ;-)  You will see in w32.c that Emacs sets
EMACSLOADPATH in the environment to the path it creates from known
directories, in order to set load-path correctly.  And GDB probably
inherits that exports it to the Emacs being debugged...

We define EMACSLOADPATH in the environment because the Windows build
doesn't want to depend on PATH_LOADSEARCH macro being set at build
time (in epaths.h), since the compiled binary needs to be able to run
on a different machine.  See init_lread.

Perhaps we should remove EMACSLOADPATH from process-environment when
we run inferior subprocesses?

reply via email to

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