nanogui: nano-X: GsRead failed -1 0: 131


Previous by date: 3 Sep 2007 02:01:54 +0100 Re: nano-X: GsRead failed -1 0: 131, mah_list1
Next by date: 3 Sep 2007 02:01:54 +0100 Re: multithreading issues, nanogui.reliableembeddedsystems.com
Previous in thread: 3 Sep 2007 02:01:54 +0100 Re: nano-X: GsRead failed -1 0: 131, mah_list1
Next in thread:

Subject: Re: [nanogui] nano-X: GsRead failed -1 0: 131
From: "Greg Haerr" ####@####.####
Date: 3 Sep 2007 02:01:54 +0100
Message-Id: <018201c7edc5$9e870ee0$2f01a8c0@HaydenLake>

> Further logging shows that it is the call to getNectEvent, and even 
> getNectEventTimeout, I sense a smell of error in the select() in uClib.

Well, the client will be hanging on a pipe read from the
network socket connection to the server.  Could be
a strange kernel issue where for some reason the
client process can't be awoken and hangs after the
other process side of the pipe is killed... ?

If you only have one application running, then you
can use the LINK_APP_INTO_SERVER option
and eliminate the pipe connection.

Regards,

Greg 


Previous by date: 3 Sep 2007 02:01:54 +0100 Re: nano-X: GsRead failed -1 0: 131, mah_list1
Next by date: 3 Sep 2007 02:01:54 +0100 Re: multithreading issues, nanogui.reliableembeddedsystems.com
Previous in thread: 3 Sep 2007 02:01:54 +0100 Re: nano-X: GsRead failed -1 0: 131, mah_list1
Next in thread:


Powered by ezmlm-browse 0.20.