nanogui: Corrupted Packet Nano-X


Previous by date: 3 Sep 2007 18:04:44 +0100 Corrupted Packet Nano-X, Detzner, Peter
Next by date: 3 Sep 2007 18:04:44 +0100 Nano-X shows "Cannot bind to named socket", Luo Yongliang
Previous in thread: 3 Sep 2007 18:04:44 +0100 Corrupted Packet Nano-X, Detzner, Peter
Next in thread: 3 Sep 2007 18:04:44 +0100 Re: Corrupted Packet Nano-X, Greg Haerr

Subject: Re: [nanogui] Corrupted Packet Nano-X
From: "Greg Haerr" ####@####.####
Date: 3 Sep 2007 18:04:44 +0100
Message-Id: <022201c7ee4c$3a411f20$2f01a8c0@HaydenLake>

> nxclient 548: Corrupted packet
Do you have an idea, why this happenes? After loading an Image from
Buffer, I take care, that freeImage is also executed as the next step -
of course after "drawImageToFit(...)"... 

This seems to be something to do with the maximum
request size packet overflowing a server buffer.
Grep the headers for a MAXREQSZ define or
something like that and increase it.  The system
is supposed to break down images into smaller
pieces but may not be for the GrDrawImageToFit function
you're using.

The overflow buffer is in nanox/srvnet.c::GsHandleClient()
IIRC.

Regards,

Greg

Previous by date: 3 Sep 2007 18:04:44 +0100 Corrupted Packet Nano-X, Detzner, Peter
Next by date: 3 Sep 2007 18:04:44 +0100 Nano-X shows "Cannot bind to named socket", Luo Yongliang
Previous in thread: 3 Sep 2007 18:04:44 +0100 Corrupted Packet Nano-X, Detzner, Peter
Next in thread: 3 Sep 2007 18:04:44 +0100 Re: Corrupted Packet Nano-X, Greg Haerr


Powered by ezmlm-browse 0.20.