-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
Fully Compatible
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Using a moved object
Using a moved object may lead to an unexpected/undefined behavior. An object is used after it's moved.
/src/mongo/db/pipeline/document_source_internal_apply_oplog_update.cpp:71: USE_AFTER_MOVE 176627 "oplogUpdate" is moved (indicated by "std::move(oplogUpdate)").
/src/mongo/db/pipeline/document_source_internal_apply_oplog_update.cpp:80: USE_AFTER_MOVE 176627 Returning while reference parameter "oplogUpdate" is in a moved state.
- is related to
-
SERVER-110130 Coverity analysis defect 176613: Using a moved object
-
- Closed
-
- related to
-
SERVER-110119 Coverity analysis defect 176642: Using a moved object
-
- Closed
-
-
SERVER-110130 Coverity analysis defect 176613: Using a moved object
-
- Closed
-
-
SERVER-110132 Coverity analysis defect 176604: Using a moved object
-
- Closed
-
-
SERVER-110133 Coverity analysis defect 176603: Using a moved object
-
- Closed
-
-
SERVER-110141 Coverity analysis defect 176586: Using a moved object
-
- Closed
-
-
SERVER-110146 Coverity analysis defect 176577: Using a moved object
-
- Closed
-
-
SERVER-110618 Coverity 7.0 QI Batch Fixes
-
- Closed
-