Since xemacs is now built as a windows app also under mingw, it pops up a new console whenever it wants to print something. Strangely, setting the CYGWIN environment variable to include "tty" (I use "binmode tty") fixes this (at least on nt/w2k). That's stange because it is supposed to make non-cygwin apps run worse... You have to restart bash (and possible win98) to make it take. That way, you should get readable error messages. They might tell you that you have caught the old "remove src/sheap-adjust.h" thingy (it happened to me until I figured out the tty stuff...). And yes, gdb is cool. If you build using the portable dumper, it even lets you debug xemacs. /dan Craig Lanning <lanning(a)scra.org&gt; writes: > I updated from CVS last night and attempted to build XEmacs. It did > ok until it started trying to run temacs.exe. Then it would give an > error dialog gox and exit. It still tried to dump xemacs.exe, but > failed because xemacs.exe was too small. > > In an effort to figure out what was happening, I ran gdb on one of the > temacs calls. What I found was that everything seemed to work fine > until memory_warnings() called start_of_data(). At that point a > console window poped up and disappeared, then gdb reported that it had > NO STACK. > > Any ideas on what is going on? > > (This is the mingw build of XEmacs on a Win98 machine.) > > Craig > > P.S. The version of gdb that comes with the Cygnus stuff is really cool. -- Dan Ola Holmsand Innehållsbolaget dan(a)innehall.com