Overview
| Comment: | OFThread: Fix setting the name on the wrong thread
The name of the thread may only be set from the thread itself. So the |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | 0.90 |
| Files: | files | file ages | folders |
| SHA3-256: |
1d0042a0406ef262acc45a17ae57c5ad |
| User & Date: | js on 2017-10-07 10:46:59 |
| Other Links: | branch diff | manifest | tags |
Context
|
2017-10-07
| ||
| 10:50 | OFThread: Mark the thread block nullable check-in: ead26485f6 user: js tags: 0.90 | |
| 10:46 | OFThread: Fix setting the name on the wrong thread check-in: 1d0042a040 user: js tags: 0.90 | |
|
2017-10-01
| ||
| 21:13 | Fix testing the wrong OFKernelEventObserver check-in: 13025565d3 user: js tags: 0.90 | |
Changes
Modified src/OFThread.h from [8bc0990f48] to [c358f93979]. [diff]
Modified src/OFThread.m from [3ff1e2b592] to [e0cab8357e]. [diff]
Modified src/threading.h from [44065a1e75] to [46db014c33]. [diff]
Modified src/threading_pthread.m from [9d56adf88b] to [7c690c290a]. [diff]
Modified src/threading_winapi.m from [f624bdcb51] to [5f1546849f]. [diff]