[issue18579] Dereference after NULL check in listobject.c merge_hi()

2013-08-13 Thread Christian Heimes
Christian Heimes added the comment: Thanks! Your analysis is plausible. I have closed the issue as "false positive". -- resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue18579] Dereference after NULL check in listobject.c merge_hi()

2013-08-05 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: According to this comment, ssb.values can be null: /* A sortslice contains a pointer to an array of keys and a pointer to * an array of corresponding values. In other words, keys[i] * corresponds with values[i]. If values == NULL, then the keys are *

[issue18579] Dereference after NULL check in listobject.c merge_hi()

2013-07-28 Thread Christian Heimes
New submission from Christian Heimes: Coverity Scan may have found an issue in listobject's merge code. I'm not familiar with the code so I don't know if ssb.value can be NULL here. 3. Condition "ssb.values != NULL", taking false branch 4. var_compare_op: Comparing "ssb.values" to null implies