Re: libc blocking functions/with_libc inside thread

Hey,

On Fri, Jun 23, 2017 at 03:21:28PM +0200, Boris Mulder wrote:

Basically if I do not use with_libc, the call to socket() will hang forever inside the first read() call to the socket file.

So, which code does your initial entrypoint execute? As I wrote before, the initial entrypoint is responsible for completing the I/O operations in Libc components. In other words, if the initial entrypoint does not block and then handle libc I/O signals, other threads blocked in the libc will never resume.

The reason I used a Genode::Thread was because openvpn already did that. Do you think using a pthread might be better in this case?

No, I was just curios ;-)

Grets