[xemacs-hg @ 2002-11-27 07:15:02 by ben] bug fixes, profiling debugging improvements configure.in: Check for GCC version and only use -Wpacked in v3. .cvsignore: Add .idb, .ilk for MS Windows VC++. cl-macs.el: Document better. cmdloop.el: Removed. Remove nonworking breakpoint-on-error now that debug-on-error works as documented. help.el: Extract out with-displaying-help-buffer into a more general mechanism. lib-complete.el: Support thunks in find-library-source-path. startup.el: Don't catch errors when noninteractive, because that makes stack traces from stack-trace-on-error useless. .cvsignore: Windows shit. alloc.c: Better redisplay-related assert. elhash.c: Comment change. eval.c: Don't generate large warning strings (e.g. backtraces) when they will be discarded. Implement debug-on-error as documented -- it will enter the debugger and crash when an uncaught signal happens noninteractively and we are --debug. Better redisplay-related asserts. frame-msw.c, frame.c, lisp.h, redisplay.c, scrollbar-gtk.c, scrollbar-x.c, signal.c, sysdep.c: Fix up documentation related to QUIT (which CANNOT garbage-collect under any circumstances), and to redisplay critical sections. lread.c: Add load-ignore-out-of-date-elc-files, load-always-display-messages, load-show-full-path-in-messages for more robust package compilation and debugging. profile.c: Overhaul profile code. Change format to include call count and be extensible for further info. Remove call-count-profile-table. Add set-profiling-info. See related profile.el changes (which SHOULD ABSOLUTELY be in the core! Get rid of xemacs-devel and xemacs-base packages *yesterday*!).

--- a/lisp/startup.el	Tue Nov 26 22:52:59 2002 +0000
+++ b/lisp/startup.el	Wed Nov 27 07:15:36 2002 +0000
@@ -538,10 +538,23 @@
     (startup-load-autoloads)
 
     (let (error-data)
-      (condition-case data
+      ;; if noninteractive, an error will kill us.  by catching and
+      ;; resignalling, we don't accomplish much, but do make it difficult
+      ;; to determine where the error really occurred.  when interactive,
+      ;; however, an error processing the command line does NOT kill us;
+      ;; instead, the error handler tries to display an error on the frame.
+      ;; In that case, we must make sure that all the remaining initialization
+      ;; gets done!!!
+      ;;
+      ;; #### A better solution in the interactive case is to use
+      ;; call-with-condition-handler, which would let us do the rest of
+      ;; the initialization AND allow the user to get an accurate backtrace.
+      (if (noninteractive)
 	  (command-line)
-	;; catch non-error signals, especially quit
-	(t (setq error-data data)))
+	(condition-case data
+	    (command-line)
+	  ;; catch non-error signals, especially quit
+	  (t (setq error-data data))))
       ;; Do this again, in case the init file defined more abbreviations.
       (setq default-directory (abbreviate-file-name default-directory))
       ;; Specify the file for recording all the auto save files of