-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Build, Developer Productivity
-
None
-
Storage Engines, Storage Engines - Foundations, Storage Engines - Persistence
-
SE Foundations - Q3+ Backlog
-
None
The error log is currently enabled only in the diagnostic mode. Ideally, we should configure whether the error log is enabled from cmake.
We should also determine what the defaults should be:
- The error log should be arguably always enabled in the diagnostic mode. Perhaps we can simply keep the current lines in error.h that enable it if HAVE_DIAGNOSTICS is enabled.
- Whether the error log is enabled in the release mode should be configurable from cmake, and it could be even enabled by default if the performance impact is negligible.
- depends on
-
WT-15426 Keep a log of errors to pinpoint the origin of the error
-
- Closed
-
- is depended on by
-
-
- Open
-
- is related to
-
WT-15432 Coverity analysis defect 176691: Invalid type in argument to printf format specifier
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
WT-15697 Change all python layered tests to use a configurable PALI
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-