On Fri, Sep 14, 2012 at 03:58:31PM +0800, Daniel Veillard wrote:
> On Fri, Sep 14, 2012 at 03:34:29PM +0800, Hu Tao wrote:
> > On Fri, Sep 14, 2012 at 03:10:13PM +0800, Daniel Veillard wrote:
> > > On Fri, Sep 14, 2012 at 02:24:15PM +0800, Hu Tao wrote:
> > > > memset before virResetError will caus
On Fri, Sep 14, 2012 at 02:24:15PM +0800, Hu Tao wrote:
> memset before virResetError will cause memory leak.
>
> virResetError and virCopyError, which calls virResetError, will do
> memset properly, so we don't have to worry about it here.
>
> ---
> src/util/virterror.c |2 --
> 1 file chan
On Fri, Sep 14, 2012 at 03:34:29PM +0800, Hu Tao wrote:
> On Fri, Sep 14, 2012 at 03:10:13PM +0800, Daniel Veillard wrote:
> > On Fri, Sep 14, 2012 at 02:24:15PM +0800, Hu Tao wrote:
> > > memset before virResetError will cause memory leak.
> > >
> > > virResetError and virCopyError, which calls v
On Fri, Sep 14, 2012 at 03:10:13PM +0800, Daniel Veillard wrote:
> On Fri, Sep 14, 2012 at 02:24:15PM +0800, Hu Tao wrote:
> > memset before virResetError will cause memory leak.
> >
> > virResetError and virCopyError, which calls virResetError, will do
> > memset properly, so we don't have to wor
On Fri, Sep 14, 2012 at 02:24:15PM +0800, Hu Tao wrote:
> memset before virResetError will cause memory leak.
>
> virResetError and virCopyError, which calls virResetError, will do
> memset properly, so we don't have to worry about it here.
Disagree, it's a public API, we can't justify behaviou
memset before virResetError will cause memory leak.
virResetError and virCopyError, which calls virResetError, will do
memset properly, so we don't have to worry about it here.
---
src/util/virterror.c |2 --
1 file changed, 2 deletions(-)
diff --git a/src/util/virterror.c b/src/util/virter