TeamForge : Post

Forum Topic - Thread blocks on sem after creation: (2 Items)

View: as

Nesredin Mahmud

07/12/2024 6:53 AM

post122564

Thread blocks on sem after creation

Event:88, Time:0.000.119us, Cycle:3cd772c1f7, CPU:4, Class:THREAD, Type:THCREATE pid:1015814 tid:1
Event:89, Time:0.000.120us, Cycle:3cd772c20f, CPU:4, Class:THREAD, Type:THRECEIVE pid:1015814 tid:1 
Event:90, Time:0.000.121us, Cycle:3cd772c22c, CPU:4, Class:THREAD, Type:THCREATE pid:1015814 tid:2
Event:91, Time:0.000.122us, Cycle:3cd772c243, CPU:4, Class:THREAD, Type:THSEM pid:1015814 tid:2 
Event:92, Time:0.000.124us, Cycle:3cd772c28b, CPU:4, Class:PROCESS, Type:PROCTHREAD_NAME

Can someone explain me if this is normal transition?

Cheers,
NM

Steven Dufresne

07/12/2024 11:57 AM

post122565

Re: Thread blocks on sem after creation

Somehow the log needs to contain information about which processes and threads exist and what states they're in at the 
beginning of the log. Instead of just containing a list of that information, the beginning of the log contains a bunch 
of manufactured events that create processes and threads and put the threads in the states they need to be in at the 
beginning of the log.

Judging by the small Event numbers you gave, 88-92, that's what this is. So at the time the log was captured, at the 
beginning of logging, the thread with thread id 2 in process 1015814 was semaphore blocked. If you load the log up into 
the IDE and look at it in the System Profiler perspective's Timeline pane, you'll see that that's the initial state of 
that thread.

So yes, it's normal. It's not a transition, it's an initial state aka the current state of the thread at the time the 
log was starting to be captured.

Return