My experience with threading in Pike is that there are at least as many
OS level threads as Pike threads, though there may be additional OS level
threads created outside of Pike itself (such as libraries and such).
Only one thread may be running code that operates on Pike data
structures at
H. William Welliver III wrote:
>On systems that don???t support naming threads, a parameter would be added
>either to the pike thread object itself or to the underlying OS thread???s
>thread specific data. In this situation, the thread name would be available
>through pike, but not in gdb, etc
I’ve been thinking about adding support for named threads and would like to get
some feedback on my proposed solution.
Named threads can be useful when, for example, debugging or printing a thread
dump. There are varying levels of OS support for named threads, ranging from
none at all (older
