[issue2443] uninitialized access to va_list

R. David Murray added the comment: Reducing the priority and updating the target releases, since from the discussion there doesn't appear to be a bug here. -- nosy: +r.david.murray priority: critical -> normal stage: -> commit review versions: +Python 2.7, Python 3.2 -Python 2.5, Pytho

[issue2443] uninitialized access to va_list

Daniel Stutzbach added the comment: Rolland, The va_list is initialized by the function that calls objargs_mktuple. va_start() and va_end() need to be called in the function that takes "..." as a parameter, and it is. Not a bug, but +1 on Alexander's patch to consolidate all the #ifdef's for

[issue2443] uninitialized access to va_list

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: release blocker -> critical ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue2443] uninitialized access to va_list

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: critical -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue2443] uninitialized access to va_list

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: What's the status of this? -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue2443] uninitialized access to va_list

Rolland Dudemaine <[EMAIL PROTECTED]> added the comment: Actually, this thing is more complex to solve than I thought. Specifically, as described in http://www.opengroup.org/onlinepubs/007908775/xsh/stdarg.h.html stdarg requires that variable argument functions have at least one fixed argument. T

[issue2443] uninitialized access to va_list

Rolland Dudemaine <[EMAIL PROTECTED]> added the comment: This is what I meant. The initialization should be done by calling va_start(count_va); as you described. In the files and lines I reported though, this is not called. I'll file a patch for it soon. --Rolland Dudemaine Alexander Belopolsky

[issue2443] uninitialized access to va_list

Christian Heimes <[EMAIL PROTECTED]> added the comment: Looks like a good idea to me -- priority: high -> critical resolution: -> accepted __ Tracker <[EMAIL PROTECTED]> __ __

[issue2443] uninitialized access to va_list

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: On the second thought the macro dance highlighted by OP belongs to pyport.h. Attached patch defines Py_VA_COPY macro and uses it to simplify va_list copying code. -- keywords: +patch Added file: http://bugs.python.org/file9

[issue2443] uninitialized access to va_list

Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: This is not a bug. All the reported functions expect va_list argument to be initialized before being called. AFAICT, they are consistently used in this way. For example, PyObject * PyObject_CallFunctionObjArgs(PyObject *callable, .

[issue2443] uninitialized access to va_list

Christian Heimes <[EMAIL PROTECTED]> added the comment: Can you provide a patch for 2.6 against the latest svn checkout of the trunk please? -- components: +Interpreter Core -Build nosy: +tiran priority: -> high __ Tracker <[EMAIL PROTECTED]>

[issue2443] uninitialized access to va_list

New submission from Rolland Dudemaine <[EMAIL PROTECTED]>: In many files, the following code is present (with slight variations, but the important part is there) : static PyObject * objargs_mktuple(va_list va) { int i, n = 0; va_list countva; PyObject *result, *tmp; #ifde