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

Segfault using older database/table

    • Type: Icon: Task Task
    • Resolution: Done
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      From Sasha:

      "This morning I updated my develop branch to reflect the changes pushed in response to the bug found by Sue (where the configuration wasn't properly propagated to do the DB). I ran it over the DB created with the old branch. Got a segfault. When I recreated the DB with the newest branch and then ran the tests, everything was fine. My guess is that because the new branch propagates configs properly and the old one did not, I had an old db with config A, but the benchmark was expecting config B. And that caused a crash."

      I'm going to followup on this.

            Assignee:
            sue.loverso@mongodb.com Susan LoVerso
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: