20,741
edits
m (→Debugging Threads: something for the Nasal console) |
m (→Race Condition ?: clarification ?) |
||
| Line 1: | Line 1: | ||
== Profiling individual threads via call() == | |||
<pre> | |||
# The extras hash can be set in several ways: as an extra argument (arg[4]) to call, | |||
# which does it locally to that context, or passed to debug.setDefaultExtra(extras), | |||
# which sets it for all contexts created in the C code (excluding threads). One can | |||
# get the current extras for a context with debug.getCurrentExtra. | |||
</pre> | |||
Is that even relevant regarding threads, can't we simply invoke call() inside a thread (or outside the newthread() invocation) in order to profile individual threads ? | |||
== Race Condition ? == | == Race Condition ? == | ||
In its current form, the test.nas script will profile the entire session - when running it, I am getting this when exiting: | In its current form, the test.nas script will profile the entire session - when running it, I am getting this when exiting: | ||