Fossil

Differences From Artifact [ee2f55a0fc]:

• File src/printf.c — part of check-in [06d4751a44] at 2018-07-15 18:31:46 on branch trunk — Improvements to error logging. Only log fossil_panic() calls, not fossil_fatal() calls. (user: drh size: 37391)

To Artifact [28b832affd]:

• File src/printf.c — part of check-in [3f5ab71744] at 2018-07-15 19:56:20 on branch trunk — Clarify the difference between fossil_fatal() and fossil_panic(). The fossil_panic() interface puts a message on the error log when generating webpages. Otherwise the two routines are identical. Convert some fossil_fatal() calls into fossil_panic() where appropriate. The goal here is to limit messages on the error log to things that require attention from the system administrator, or represent bugs. (user: drh size: 37727) [more...]

1057
1058
1059
1060
1061
1062
1063






1064
1065
1066
1067
1068
1069
1070

1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076

+
+
+
+
+
+

  }
  return rc;
}

/*
** Print an error message, rollback all databases, and quit.  These
** routines never return.
**
** The only different between fossil_fatal() and fossil_panic() is that
** fossil_panic() makes an entry in the error log whereas fossil_fatal()
** does not.  If there is not error log, then both routines work the
** same.  Hence, the routines are interchangable for commands and only
** make a difference with processing web pages.
**
** Use fossil_fatal() for malformed inputs that should be reported back
** to the user, but which do not represent a configuration problem or bug.
**
** Use fossil_panic() for any kind of error that should be brought to the
** attention of the system administrator.
*/