[issue32681] Fix uninitialized variable in os_dup2_impl

Change by Gregory P. Smith : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue32681] Fix uninitialized variable in os_dup2_impl

Gregory P. Smith added the comment: New changeset 3d86e484de6334fe16cbab512744597bd0de4e80 by Gregory P. Smith (Stéphane Wirtel) in branch 'master': bpo-32681: Fix an uninitialized variable in the C implementation of os.dup2 (GH-5346) https://github.com/python/cpython/commit/3d86e484de6334fe1

[issue32681] Fix uninitialized variable in os_dup2_impl

Change by Stéphane Wirtel : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue32681] Fix uninitialized variable in os_dup2_impl

Stéphane Wirtel added the comment: Yes, you can close it, but I don't understand why there is no fix for this warning. my issue has a small PR, but the other issue on b.p.o, I am not really sure about my fix... I just set the 'res' variable to 0 and avoid this kind of message. Is there an other

[issue32681] Fix uninitialized variable in os_dup2_impl

Change by Stéphane Wirtel : -- keywords: +patch pull_requests: +5194 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-l

[issue32681] Fix uninitialized variable in os_dup2_impl

STINNER Victor added the comment: I already reported the issue at: https://bugs.python.org/issue32441#msg310752 I suggest to close this issue as a duplicate. -- nosy: +vstinner ___ Python tracker ___

[issue32681] Fix uninitialized variable in os_dup2_impl

New submission from Stéphane Wirtel : With the last revision, I get this warning from the compiler. gcc -pthread -Wno-unused-result -Wsign-compare -g -Og -Wall -Wstrict-prototypes -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-func