-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Not Applicable
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - 2025-09-12
-
1
In the (alleged) fix to WT-15173, an error was introduced. When reallocing zero elements, realloc returns NULL, and it is not an error. Dying at that point is not the right thing to do.
A clean and general fix is to modify drealloc to allow a NULL return (without error) if zero elements is allocated. Same with dmalloc, dcalloc.
- is related to
-
WT-15173 Coverity analysis defect 175782: Dereference null return value
-
- Closed
-
-
WT-15247 Unexpected keys observed after connection reopen for disagg
-
- Closed
-
-
WT-15249 Add error check for incompatible config with write_timestamp_usage=never in disagg
-
- Closed
-
-
WT-15396 Coverity analysis defect 175990: Calling risky function
-
- Closed
-
-
WT-15405 Fix layered table key deletion and add a test for GC
-
- Closed
-
-
WT-15401 Make test/model compatible with macOS
-
- Closed
-
-
WT-15389 Saved update lists with deletes are lost when building a delta
-
- Closed
-
- related to
-
WT-14904 Add more scenarios for the internal page deltas
-
- Closed
-
-
WT-15213 Don't free the previous address cookie
-
- Closed
-
-
WT-15187 Don't build overflow keys or values in disagg
-
- Closed
-