Christopher Tate 41c4bea27c Don't accidentally signal multiple exceptions in setThreadPriority()
After signalling an exception due to set_sched_policy() failing (probably
because the thread in question had exited before this function was called), we
proceeded to call setpriority() anyway, and raised *another* exception when it
also failed.  We don't do this any more; we just bail after signalling the first
exception.

Change-Id: I397b6a93c73d3f0870176e26759f2bec33e56205
2009-12-04 11:07:48 -08:00
2009-12-03 14:13:53 -08:00
2009-11-23 17:26:37 -08:00
2009-12-03 16:06:52 -08:00
2009-12-03 16:15:46 -08:00
2009-12-03 10:24:18 -08:00
2009-12-02 17:39:27 -08:00
2009-11-16 17:59:32 -08:00
Description
No description provided
5.1 GiB
Languages
Java 77.3%
Kotlin 9.2%
PowerBuilder 6.6%
C++ 5.5%
AIDL 1%