Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
Developer Tools
-
ALL
-
Platforms 2018-04-23
Description
The libmongodbcapi contains a whole bunch of unfortunate coding constructs such as
} catch (const std::exception&) {
|
last_error = LIBMONGODB_CAPI_ERROR_UNKNOWN;
|
return nullptr;
|
}
|
This paradigm of coding, coupled with the prevalent use of uasserts in the client/embedded/ codebase, results in a frustrating (and time consuming) debugging experience for anyone who happens to have a patch build fail a test in this area. Could we add better exception handling in this library?
Attachments
Issue Links
- duplicates
-
SERVER-33909 Provide more detailed error reporting from CAPI
-
- Closed
-