This application has some 14 processes, each with a thread
or two, sometimes more.
There is a main_task which launches each of the other tasks.
How can I get the IDE to attach to each process in this
project?
At the moment I can only get profiling info on the main_task,
(by launching a debug session on it by name)
and for the others I launch a separate debug
session and attach to the remote process(es).
This doesn’t allow me to get the low level function calls
info on the remotely attached processes.
This application has some 14 processes, each with a thread
or two, sometimes more.
There is a main_task which launches each of the other tasks.
How can I get the IDE to attach to each process in this
project?
At the moment I can only get profiling info on the main_task,
(by launching a debug session on it by name)
and for the others I launch a separate debug
session and attach to the remote process(es).
This doesn’t allow me to get the low level function call
info on the remotely attached processes.
Firstly make sure they are compiled and linked with profiling. Secondly,
when these sub tasks are run, make sure that the env. var. QCONN_PROFILER
is set to /dev/profiler, also make sure they don’t close any fds on startup
(e.g. calling procmgr_deamon(…) without PROCMGR_DAEMON_NOCLOSE flag is bad).
On Tue, 22 Apr 2003 08:43:58 -0400, David Inglis <dinglis@qnx.com> wrote:
acellarius@yahoo.com > wrote:
This application has some 14 processes, each with a thread
or two, sometimes more.
There is a main_task which launches each of the other tasks.
How can I get the IDE to attach to each process in this
project?
At the moment I can only get profiling info on the main_task,
(by launching a debug session on it by name)
and for the others I launch a separate debug
session and attach to the remote process(es).
This doesn’t allow me to get the low level function call
info on the remotely attached processes.
Firstly make sure they are compiled and linked with profiling. Secondly,
when these sub tasks are run, make sure that the env. var. QCONN_PROFILER
is set to /dev/profiler, also make sure they don’t close any fds on startup
(e.g. calling procmgr_deamon(…) without PROCMGR_DAEMON_NOCLOSE flag is bad).
Thanks-I can see multiple proceesses ok now with full level of detail.
Is there a place somewhere where I can find out more?
Where is a good place to put the env variable?
export QCONN_PROFILER=/dev/profiler in /rc.local doesn’t do it for me.
Thanks for the help!