<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - The tutorial should have a section on error handling" href="https://bugs.freedesktop.org/show_bug.cgi?id=78140#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - The tutorial should have a section on error handling" href="https://bugs.freedesktop.org/show_bug.cgi?id=78140">bug 78140</a> from <a class="email" href="mailto:sstewartgallus00@mylangara.bc.ca" title="Steven Stewart-Gallus <sstewartgallus00@mylangara.bc.ca>"> Steven Stewart-Gallus</a> <pre>I find it unfortunate that xcb_disconnect does not return an error code. First of all, the close and EINTR problem is easily solvable. Simply, block all signals while closing a file and then the EINTR error can never happen. Second of all, an obvious thing to do if close fails in a process is to exit the process and disable that part of the system but keep the rest of the system running (that way someone can run a debug console later on and diagnose and fix the problem or recover data if the system is truely broken). Simply going on instead is wrong because that might result in corrupting user data. I'd even rather have the function abort on errors then simply ignore them. Thirdly, pthread_mutex_destroy and pthread_cond_destroy should not fail with errors on proper use of their functionality so they are irrelevant.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>