Hi Joel,
Yes, such “topology” information is stored in the agent so that the point in time when a client attaches does not matter. The client just needs to use the RunControl service to get the topology.
Yes, the initialization/discovery logic should create the “already existing” contexts (processes/threads in your case) in the topology.
Thank you.
The VxWorks task_create_hookd only puts a task Id and TCB pointer in the Context. I see a name field which makes sense to fill in. Is any of the other information in the Context assumed to be filled in by the target?
This certainly gives me something to work on until the list of threads shows up in the UI.
Thanks.
Cheers,
- Mircea
From: tcf-dev-bounces@xxxxxxxxxxx <tcf-dev-bounces@xxxxxxxxxxx> On Behalf Of Joel Sherrill
Sent: Tuesday, November 3, 2020 3:03 PM
To: TCF Development <tcf-dev@xxxxxxxxxxx>
Subject: [tcf-dev] Being Aware of Threads Created Before Agent is Initialized
Hi
Looking at context-vxworks.c, it creates an event handling thread and registers a task create hook. Some tasks will have been created before this code is executed. Will those threads not show up in the explorer view? Should the initialization attempt to register Contexts for all existing threads?
Do these events just build up information inside the agent which the client-side can ask for later? I am thinking the agent is often started without a UI attached.
I've never used VxWorks so my questions may be wrong if I am reading something into the code that's not there. :)
Thanks.
--joel
