On Wed, Sep 30, 2009 at 03:09:29PM +0100, Daniel P. Berrange wrote:
> On Wed, Sep 30, 2009 at 03:51:21PM +0200, Daniel Veillard wrote:
> > On Wed, Sep 30, 2009 at 02:34:46PM +0100, Daniel P. Berrange wrote:
> > > The code which updated the message length after writing the
> > > payload wrote the up
On Wed, Sep 30, 2009 at 03:51:21PM +0200, Daniel Veillard wrote:
> On Wed, Sep 30, 2009 at 02:34:46PM +0100, Daniel P. Berrange wrote:
> > The code which updated the message length after writing the
> > payload wrote the updated length word in the wrong place since
> > the XDR object was given a bu
On Wed, Sep 30, 2009 at 02:34:46PM +0100, Daniel P. Berrange wrote:
> The code which updated the message length after writing the
> payload wrote the updated length word in the wrong place since
> the XDR object was given a buffer pointing to the start of the
> header payload, rather than message s
The code which updated the message length after writing the
payload wrote the updated length word in the wrong place since
the XDR object was given a buffer pointing to the start of the
header payload, rather than message start.
* daemon/remote.c: Fix updating of event message length so that
we
