TeamForge : Post

Forum Topic - tracing user events:

View: as

Sebastian Fischmeister(deleted)

11/01/2013 10:05 PM

post106486

When running tracelogger with these filter options, it seems that the USREVENTS are not captured. This seems incorrect, 
because USREVENT is different class than the ones that get filtered with F1 to F7. Enabling one of the options also 
starts recording the USREVENT class.

Test it with:

tracelogger -F1 -F2 -F3 -F4 -F6 -F7 -s 3
./start_your_program_that_uses_trace_logi_while_trace_gets_logged
traceprinter | grep USREVENT

Colin Burgess(deleted)

11/02/2013 10:08 AM

post106488

Re: tracing user events

How many user events did you emit?  Did you stop tracelogger? Sounds 
like the buffer wasn't flushed.

On 2013-11-01 10:05 PM, Sebastian Fischmeister wrote:
> When running tracelogger with these filter options, it seems that the USREVENTS are not captured. This seems incorrect
, because USREVENT is different class than the ones that get filtered with F1 to F7. Enabling one of the options also 
starts recording the USREVENT class.
>
> Test it with:
>
> tracelogger -F1 -F2 -F3 -F4 -F6 -F7 -s 3
> ./start_your_program_that_uses_trace_logi_while_trace_gets_logged
> traceprinter | grep USREVENT
>
>
>
>
>
>
> _______________________________________________
>
> QNX Momentics Getting Started
> http://community.qnx.com/sf/go/post106486
> To cancel your subscription to this discussion, please e-mail momenticsgs-community-unsubscribe@community.qnx.com

Sebastian Fischmeister(deleted)

11/02/2013 10:13 AM

post106489

Re: tracing user events

> How many user events did you emit?  Did you stop tracelogger? Sounds 
> like the buffer wasn't flushed.

I emitted about 12 user events. However, since I run tracelogger with the option of '-s 3', I assume that it would force
 a buffer flush before it terminates, woudn't it?

  Sebastian

Colin Burgess(deleted)

11/02/2013 10:18 AM

post106490

Re: tracing user events

Which version of tracelogger are you using?  There was a fix made in 
2011 that addressed this.

Try adding TraceEvent(_NTO_TRACE_FLUSHBUFFER) to your app...

On 2013-11-02 10:13 AM, Sebastian Fischmeister wrote:
>> How many user events did you emit?  Did you stop tracelogger? Sounds
>> like the buffer wasn't flushed.
> I emitted about 12 user events. However, since I run tracelogger with the option of '-s 3', I assume that it would 
force a buffer flush before it terminates, woudn't it?
>
>    Sebastian
>
>
>
> _______________________________________________
>
> QNX Momentics Getting Started
> http://community.qnx.com/sf/go/post106489
> To cancel your subscription to this discussion, please e-mail momenticsgs-community-unsubscribe@community.qnx.com

Sebastian Fischmeister(deleted)

11/02/2013 10:25 AM

post106491

Re: tracing user events

I use 6.5.0 SP1.

Adding the explicity flush solves the problem. Thanks.

> Which version of tracelogger are you using?  There was a fix made in 
> 2011 that addressed this.
> 
> Try adding TraceEvent(_NTO_TRACE_FLUSHBUFFER) to your app...
> 
> On 2013-11-02 10:13 AM, Sebastian Fischmeister wrote:
> >> How many user events did you emit?  Did you stop tracelogger? Sounds
> >> like the buffer wasn't flushed.
> > I emitted about 12 user events. However, since I run tracelogger with the 
> option of '-s 3', I assume that it would force a buffer flush before it 
> terminates, woudn't it?
> >
> >    Sebastian
> >
> >
> >
> > _______________________________________________
> >
> > QNX Momentics Getting Started
> > http://community.qnx.com/sf/go/post106489
> > To cancel your subscription to this discussion, please e-mail momenticsgs-
> community-unsubscribe@community.qnx.com
>

Return