Dump memory region containing "illegal value" whenever it's possible

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Tools
    • None
    • Storage Engines - Persistence
    • 3,538.808
    • SE Persistence backlog
    • None

      This is a follow-up ticket to BF-40058.

      BF-40058 is likely a collection of failures caused by memory corruption, possibly due to a use-after-free error.

      To improve diagnostics, whenever an illegal value is detected in a memory region (e.g. page type, cell type, etc.), we should dump the entire memory region along with the value's offset and size within that region (for example, the entire page).
      This will help us identify the nature and source of the corruption more effectively.

      Add a new function: __wt_illegal_value_in_block(session, v, mem, size, offset) and replace calls to __wt_illegal_value(session, v) where applicable.

            Assignee:
            Unassigned
            Reporter:
            Yury Ershov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: