Some time ago, Mike Alexander wrote...
This patch changes pdump_load on Windows so that it finds the .dmp
file by changing the ".exe" at the end of the path XEmacs was launched from to
".dmp". Previously it was looking in the current working directory for
xemacs.dmp. It doesn't seem like a good idea to depend on the CWD being correct, even
if it usually is (it wasn't in my debug setup). If the path is very long or
doesn't end in ".exe" it falls back to the previous way of finding the dump
file. I imagine a similar hack could be done on Unix, but I'm not familiar enough
with the various flavors supported by XEmacs to know the best way to do it.
I think that this fix is not correct. We should not employ different
mechanisms for finding the dmp file on different OSes.
Definition of "very long path" as being longer than the arbitrary
integer 256 is absolutely incorrect either.
I has not been following the discussion on *how* to locate the dmp
file. Has there been a consensus on that? What I propose is really
what Mike did, look for the file in the same directory where xemacs
binary is installed, unless overridden by a command line switch.
Big K