Re: [Success with Workaround] XEmacs 21.5-b25 "eggplant" (+CVS-20060305) i586-pc-win32

>>>>>"APA" == Adrian Aichner <adrian(a)xemacs.org&gt; writes: APA> I tracked down the native Windows compiler error APA> c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src\glyphs-widget.c(1772) : fatal error C1001: INTERNAL COMPILER ERROR APA> (compiler file 'msc1.cpp', line 1794) APA> Please choose the Technical Support command on the Visual C++ APA> Help menu, or open the Technical Support help file for more information APA> NMAKE: fatal error U1077: 'cl' : return code '0x2' APA> Stop. This compiler error only occurs when I compile NEW_GC together with UNION_TYPE=1, DEBUG_XEMACS=1, and OPTIMIZED_BUILD=1. Please don't compile NEW_GC together with UNION_TYPE, DEBUG_XEMACS, and OPTIMIZED_BUILD. Especially, please don't use NEW_GC together with OPTIMIZED_BUILD, to keep backtraces clean.

APA> It runs slowly, APA> Is ERROR_CHECKING causing a lot more GC? APA> Looks like from a bit of testing. No, it doesn't GC more, it error checks more. APA> M-x show-memory-usage reports have been useless for quite a while. APA> ISTR Stephen reported this before. I missed Stephen's report, sorry. APA> Why has the object memory usage report become basically useless? Because I broke it a few months ago. I'll commit a patch in a bit. BTW, show-object-memory-usage-stats always worked.