Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-10134

Segfault in __rec_append_orig_value on 4.4.14

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None

      It's possible to segfault in __rec_append_orig_value in non diagnostic builds on line 129 of rec_visibility.c here. This would require the expected on disk value unpack to be NULL or its associated time window.

          if (WT_TIME_WINDOW_HAS_STOP(&unpack->tw)) {
              tombstone_globally_visible = __wt_txn_tw_stop_visible_all(session, &unpack->tw);
      

      Given that this happened on 4.4.14 the code has changed significantly including the addition of a WT_ASSERT_ALWAYS prior which checks that the unpack isn't NULL.

      This ticket is intended to track this failure mode as I couldn't find existing or resolved WT issue that show this or a similar failure mode.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            luke.pearson@mongodb.com Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: