nano-X: GsHandleClient request too large:

[David Siebert]

Yes I did set THREADSAFE=Y I will double check it.

: I am just drawing a series of strings. Would adding a GrFlush between
: strings potently solve the problem?
Not likely, try it
: It is multi-threaded if you think that might be an issue.
that's definitely the issue, the threads are mixing requests.
The only sure way of fixing this, assuming you've already
set THREADSAFE=Y in the config file, is to have only
a single thread issue NX requests. Trouble starts when
requests are sent which require replies, and thats when the
sync problems start. The THREADSAFE option ensures
that nano-X handles reentrancy issues within the nano-X
client library, but that's all.
Regards,
Greg

[Greg Haerr]

: I am just drawing a series of strings. Would adding a GrFlush between
: strings potently solve the problem?

Not likely, try it


: It is multi-threaded if you think that might be an issue.

that's definitely the issue, the threads are mixing requests.
The only sure way of fixing this, assuming you've already
set THREADSAFE=Y in the config file, is to have only
a single thread issue NX requests. Trouble starts when
requests are sent which require replies, and thats when the
sync problems start. The THREADSAFE option ensures
that nano-X handles reentrancy issues within the nano-X
client library, but that's all.

Regards,

Greg

[Greg Haerr]

: I am getting this error and my application is locking up. Any ideas what

: could be causing this.

You are likely sending an image that is larger than the stack
allocated in the server, see nanox/srvnet.c::GsHandleClientRequest()
or something like that, there's a define MAXSTACKSZ or
MAXCLIENTRQSIZE or something to that effect that
needs to be made bigger.

Actually, the system is supposed to cut images down to this
size (see nanox/client.c), perhaps something isn't working
as designed. You can enable a DPRINTF in the
above function and it will display what function the
system is dying on, and then you might change your
application or increase a nanox/nxproto.h parameter.

Regards,

Greg

[David Siebert]

Greg Haerr wrote:
I am just drawing a series of strings. Would adding a GrFlush between
strings potently solve the problem?
It is multi-threaded if you think that might be an issue.

Post by Greg Haerr

: I am getting this error and my application is locking up. Any ideas what

: could be causing this.
You are likely sending an image that is larger than the stack
allocated in the server, see nanox/srvnet.c::GsHandleClientRequest()
or something like that, there's a define MAXSTACKSZ or
MAXCLIENTRQSIZE or something to that effect that
needs to be made bigger.
Actually, the system is supposed to cut images down to this
size (see nanox/client.c), perhaps something isn't working
as designed. You can enable a DPRINTF in the
above function and it will display what function the
system is dying on, and then you might change your
application or increase a nanox/nxproto.h parameter.
Regards,
Greg

[David Siebert]

I am getting this error and my application is locking up. Any ideas what
could be causing this.