[SERVER-56591] Coverity analysis defect 120008: Explicit null dereferenced Created: 03/May/21 Updated: 27/Oct/23 Resolved: 18/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Coverity Collector User | Assignee: | Kyle Suarez |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | coverity | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Sprint: | Query Execution 2021-05-31 |
| Participants: |
| Description |
|
Explicit null dereferenced A null pointer dereference will occur. Dereference of an explicit null value |
| Comments |
| Comment by Kyle Suarez [ 18/May/21 ] |
|
After discussion at Query Execution triage we've decided this is works as designed. I've also gone into Coverity to mark it as a false positive. |
| Comment by Kyle Suarez [ 12/May/21 ] |
|
Per an offline discussion with martin.neupauer, we have a suspicion that this is a false positive from Coverity. I'm sending this back to the Query Execution triage queue to discuss next steps. |
| Comment by Kyle Suarez [ 04/May/21 ] |
|
I feel like atEnd() does not actually dereference _arrayCurrent because _arraySet is non-null when the type tag is ArraySet but it would be good for someone to take a more thorough look and confirm. |