af426c7aa40aad4c5c6b532b02a1151dd42da305
galt
  Wed Jun 4 15:17:14 2014 -0700
Inside an errCatch block warnings which are not followed by an errAbort just get swallowed up and ignored. I added a flag to the structure that remembers that warnings have occurred.
diff --git src/lib/errabort.c src/lib/errabort.c
index 46ddb3b..7eb6ec0 100644
--- src/lib/errabort.c
+++ src/lib/errabort.c
@@ -1,20 +1,23 @@
-/* ErrAbort.c - our error handler.
+/* errabort.c - our error handler.
  *
  * This maintains two stacks - a warning message printer
  * stack, and a "abort handler" stack.
  *
+ * Note that the abort function always calls the warn handler first.
+ * This is so that the message gets sent.
+ *
  * By default the warnings will go to stderr, and
  * aborts will exit the program.  You can push a
  * function on to the appropriate stack to change
  * this behavior.  The top function on the stack
  * gets called.
  *
  * This file is copyright 2002 Jim Kent, but license is hereby
  * granted for all use - public, private or commercial. */
 
 // developer: this include is for an occasionally useful means of getting stack info without
 // crashing
 // however, it is not supported on cygwin.  Conditionally compile this in when desired.
 //#define BACKTRACE_EXISTS
 #ifdef BACKTRACE_EXISTS
 #include <execinfo.h>