Re: System calls without error checks in w32

[Eli Zaretskii]

> From: Lennart Borgman <address@hidden>
> Date: Sat, 29 May 2010 20:42:40 +0200
> Cc: address@hidden
> 
> CreateFontIndirect
> DestroyCaret
> ExtTextOut
> GetForeGroundWindow
> GetKeyboardState
> GetKeyboardState
> GetModuleHandle
> GetProcAddress
> GetTextExtentPoint32
> GetWindowPlacement
> GetWindowRect
> KillTimer
> LocalFree
> PostMessage
> PostThreadMessage
> RegisterHotKey
> ReleaseCapture
> SelectObject
> SetWindowLong
> 
> A few of them does not return errors, but return value may have to be
> checked anyway.

If you can suggest what to do when any of these fails, please do.

> >>     DebPrint (("error w32_creatwindow.AjdustRectangle => %d\n",
> >> GetLastError ()));
> >>
> >> to all of them? Is there anyone who has anything against this?
> >
> > What for?
> 
> 
> I have for several years complained about frequent crashes. They are
> quite irritating actually.
> 
> I have to reboot quite often too, maybe because of errors in the
> system calls (some resource is leaking).
> 
> Menus often stops working. Difficult to track down, and even more so
> without knowing if some bad system calls where involved.
> 
> Emacs can totally hang. Or it can loop without yeilding. At least the
> first one can be a bad system call.

I don't see how any of these problems could be solved by using
DebPrint.