2014-07-08 1:48 GMT+04:00, Martin Decky <[email protected]>: > Of course, the connection is also closed if you exit the > client_connection() routine.
It was my second assumption which I didn't checked. > Now, can you provide me with a test case where the bug you describe > actually happens? I know that you have written in the other thread that > you have added the all-zeroes mode in vesafb to workaround it. But I > can't find this workaround in order to undo it and see what happens > without it. All-zeroes mode is interpreted by compctl as a signal to stop looping. Just remove this terminating mode in vesafb and compositor will hang after the last mode had printed by compctl. I suppose it happens after vs_enumerate_modes() fail to get out-of-range list element in modes list and will return non-EOK status. > BTW: This is probably not related, but the client-side pattern in > compctl.c is not entirely correct. You should not create an exchange > before the for-loop and then call multiple async_req_*() in the loop. > The exchange is used to group multiple calls that together create a > single logical call. But in this case you are doing multiple independent > calls, thus the code should look like this: I did so at first by then decided to save instructions. Can we threat loop as a single logical session? _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
