[issue41059] Large number of Coverity reports for parser.c

Change by Guido van Rossum : -- resolution: -> works for me stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ __

[issue41059] Large number of Coverity reports for parser.c

Lysandros Nikolaou added the comment: I propose that we take no further action and close this. -- ___ Python tracker ___ ___ Python

[issue41059] Large number of Coverity reports for parser.c

Pablo Galindo Salgado added the comment: I tried reprodicing the coverity results using cppcheck (I don't have access to the coverity project, someone needs to approve :() and I got just a dozen of results: ❯ cppcheck Parser/parser.c --enable=style Checking Parser/parser.c ... Parser/parser.c

[issue41059] Large number of Coverity reports for parser.c

Change by Gregory P. Smith : -- nosy: +christian.heimes ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue41059] Large number of Coverity reports for parser.c

Guido van Rossum added the comment: Good catch! Are all the coverity complaints about this kind of code? if (_res == NULL && PyErr_Occurred()) { ... } (Mostly for Pablo and Lysandros:) This comes from emit_action(). It is preceded by a line of the form _res = ; Most of the time the ac

[issue41059] Large number of Coverity reports for parser.c

Change by Paul Ganssle : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue41059] Large number of Coverity reports for parser.c

Change by Gregory P. Smith : -- components: +Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41059] Large number of Coverity reports for parser.c

New submission from Gregory P. Smith : Here's an example: *** CID 1464688: Control flow issues (DEADCODE) /Parser/parser.c: 24243 in _tmp_147_rule() 24237 && 24238 (z = disjunction_rule(p)) // disjunction 24239 ) 24240 { 24241