Re: [xml] reproducible coredump libxml2-2.3.8, trio or libxml or both
- From: xml thewrittenword com
- To: xml gnome org
- Subject: Re: [xml] reproducible coredump libxml2-2.3.8, trio or libxml or both
- Date: Thu, 31 May 2001 11:09:27 -0500
On Thu, May 31, 2001 at 04:00:18PM +0000, Bjorn Reese wrote:
[ Apologies if this email appears twice. Due to problems with Adam Clarke's
address, my first reply was rejected by my mailserver. In this second
reply, I removed his address from the cc: list ]
Daniel Veillard wrote:
Well, clearly xmlGetVarStr() expect args to not have been changed in
case of unsifficient lenght of the formatting buffer.
And unfortunately this is exactly the problem.
C99 (section 7.15.2) states that "The object ap [va_list argument] may
be passed as an argument to another function; if that function invokes
the va_arg macro with parameter ap, the value of ap in the calling
function is indeterminate and shall be passed to the va_end macro
prior to any futher reference to ap".
Furthermore, C99 description of vsnprintf (section 22.214.171.124) says that
"The vnsprintf function does not invoke the va_end macro", followed by
a footnote that says "As [...] vnsprintf [...] invoke the va_arg macro,
the value of the arg[ument] after the return is indeterminate".
In summary, the use of vsnprintf in xmlGetVarStr is "too creative".
Making a workaround in trio does not help on the platforms where
trio_vsnprintf is not used.
And what does C89 say? I wouldn't assume that a system needing
trio_vsnprintf has a C99-compliant compiler.
albert chin (china thewrittenword com)
] [Thread Prev