Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Instrumented kernel usage with debugger: (4 Items)
   
Instrumented kernel usage with debugger  
Hello, i would like to use the instrumented kernel to check threads execution in my application in debug mode. I have 
set up the onboard to use tracelogger, etc. But i have no ideas when should i start the program such that the 
tracelogger will log the time period that i am really interested. Btw, the time option in tracelogger must be set to 
avoid the default 0 second?

Thanks,
Eric
Re: Instrumented kernel usage with debugger  
the best way to do this is to start tracelogger in daemon mode, where it is ready to go but not logging.

eg

# tracelogger -d1 -E -w -c -S32M -M -v &

and then in your application, start tracing with

TraceEvent( _NTO_TRACE_START );

and stop with

TraceEvent( _NTO_TRACE_STOP );
TraceEvent( _NTO_TRACE_FLUSHBUFFER ); /* make sure to get the last partial buffer out */

Eric Dong wrote:
> Hello, i would like to use the instrumented kernel to check threads execution in my application in debug mode. I have 
set up the onboard to use tracelogger, etc. But i have no ideas when should i start the program such that the 
tracelogger will log the time period that i am really interested. Btw, the time option in tracelogger must be set to 
avoid the default 0 second?
> 
> Thanks,
> Eric
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post28004
> 

-- 
cburgess@qnx.com
Re: Instrumented kernel usage with debugger  
Thanks, but may i know the meaning of -E and -c ? I am using QNX 6.3.2.

Eric

> the best way to do this is to start tracelogger in daemon mode, where it is 
> ready to go but not logging.
> 
> eg
> 
> # tracelogger -d1 -E -w -c -S32M -M -v &
> 
> and then in your application, start tracing with
> 
> TraceEvent( _NTO_TRACE_START );
> 
> and stop with
> 
> TraceEvent( _NTO_TRACE_STOP );
> TraceEvent( _NTO_TRACE_FLUSHBUFFER ); /* make sure to get the last partial 
> buffer out */
> 
> Eric Dong wrote:
> > Hello, i would like to use the instrumented kernel to check threads 
> execution in my application in debug mode. I have set up the onboard to use 
> tracelogger, etc. But i have no ideas when should i start the program such 
> that the tracelogger will log the time period that i am really interested. Btw
> , the time option in tracelogger must be set to avoid the default 0 second?
> > 
> > Thanks,
> > Eric
> > 
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post28004
> > 
> 
> -- 
> cburgess@qnx.com


Re: Instrumented kernel usage with debugger  
I believe they were added in 640

-E enables all events
-c is the equivalent to -n0

without -E you would also have to add

TraceEvent( _NTO_TRACE_ADDALLCLASSES );

to your code, before the _NTO_TRACE_START call.

You should also call

TraceEvent( _NTO_TRACE_DELALLCLASSES ); after the stop too.

Colin

Eric Dong wrote:
> Thanks, but may i know the meaning of -E and -c ? I am using QNX 6.3.2.
> 
> Eric
> 
>> the best way to do this is to start tracelogger in daemon mode, where it is 
>> ready to go but not logging.
>>
>> eg
>>
>> # tracelogger -d1 -E -w -c -S32M -M -v &
>>
>> and then in your application, start tracing with
>>
>> TraceEvent( _NTO_TRACE_START );
>>
>> and stop with
>>
>> TraceEvent( _NTO_TRACE_STOP );
>> TraceEvent( _NTO_TRACE_FLUSHBUFFER ); /* make sure to get the last partial 
>> buffer out */
>>
>> Eric Dong wrote:
>>> Hello, i would like to use the instrumented kernel to check threads 
>> execution in my application in debug mode. I have set up the onboard to use 
>> tracelogger, etc. But i have no ideas when should i start the program such 
>> that the tracelogger will log the time period that i am really interested. Btw
>> , the time option in tracelogger must be set to avoid the default 0 second?
>>> Thanks,
>>> Eric
>>>
>>> _______________________________________________
>>> General
>>> http://community.qnx.com/sf/go/post28004
>>>
>> -- 
>> cburgess@qnx.com
> 
> 
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post28030
> 

-- 
cburgess@qnx.com