Add assertions for non-null client and pool parameters

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Minor - P4
    • 1.24.0
    • Affects Version/s: None
    • Component/s: libmongoc
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After CDRIVER-3723, client and pool constructors will return NULL in more situations (e.g. invalid topology). In applications that were not already checking for NULL return values, this could lead to unexpected segfaults. We should consider adding assertions to functions that take client and pool parameters to mitigate this risk.

            Assignee:
            Josh Siegel
            Reporter:
            Jeremy Mikola
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: