Confirmed users
69
edits
(→ack: added .rc files) |
No edit summary |
||
| Line 158: | Line 158: | ||
Now when you're in the debugger, you can examine the mMutex (which is a pthread_mutex_t) and grab the value field (the only field inside the pthread_mutex_t). The upper 16 bits will contain the thread id of the mutex holder. In gdb, you can use "info threads" to see all of the running threads, and you can use the "thread number" command to switch between threads (to examine the backtrace etc). | Now when you're in the debugger, you can examine the mMutex (which is a pthread_mutex_t) and grab the value field (the only field inside the pthread_mutex_t). The upper 16 bits will contain the thread id of the mutex holder. In gdb, you can use "info threads" to see all of the running threads, and you can use the "thread number" command to switch between threads (to examine the backtrace etc). | ||
==Running updater xpcshell tests locally== | |||
I was working on the updater, and its useful to be able to run xpcshell tests locally. So here's my [[DHylands_updater_xpcshell|updater xpcshell]] page. | |||