[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

Pablo Galindo Salgado added the comment: Thanks for the time detecting this, opening this issue and the PR (and all the others), Stéphane! :) -- ___ Python tracker ___ ___

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

Stéphane Wirtel added the comment: That was funny to use gdb and valgrind for the debugging session. Now I can help you for the refleaks ;-) -- ___ Python tracker ___

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

Stéphane Wirtel added the comment: Yep, Victor has started the refactoring/cleaning after my PR, but I close this one and the issue. -- stage: -> resolved status: open -> closed ___ Python tracker _

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

Pablo Galindo Salgado added the comment: This issue is already been handled in https://github.com/python/cpython/pull/12441 -- nosy: +pablogsal ___ Python tracker ___ ___

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

Change by Stéphane Wirtel : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

Stéphane Wirtel added the comment: @vstinner I just initialized argv0 to NULL but the wcsrchr could generate a SIGSEGV. What do you suggest for the initial value of argv0? try to detect the sys.executable and use it for argv0? -- stage: patch review -> _

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

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

[issue36308] Fix warning in _PyPathConfig_ComputeArgv0

New submission from Stéphane Wirtel : Python/pathconfig.c: In function '_PyPathConfig_ComputeArgv0': Python/pathconfig.c:615:26: warning: 'argv0' may be used uninitialized in this function [-Wmaybe-uninitialized] wchar_t *q = wcsrchr(argv0, SEP); ^~