Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - reported event time (re)starts with zero on every new tracebuffer in a kev file: (14 Items)
   
reported event time (re)starts with zero on every new tracebuffer in a kev file  
already posted this weeks ago, but nobody replied.
so after installing the latest build 200802041024 - I tried adain,  but sill ...

The shown time of an event in the "Trace Log" view starts with zero on every new tracebuffer.
see here:
Event, Time, Owner, Type, Data
293815, 999ms 995us, MMI3GApplication (77854) Thread 7 (7), SyncSemPost Enter, sync_ptr 0x803aa2c count 0 owner 
0xfffffffc
293816, , MMI3GApplication (77854) Thread 14 (14), Ready, pid 77854 tid 14 priority 15 policy 2
293817, 2us, MMI3GApplication (77854) Thread 7 (7), SyncSemPost Exit, ret_val 0x0

this is not very handy, 'cause you can't use this information anymore
and using "Real Time" instead is not really an option.
Re: reported event time (re)starts with zero on every new tracebuffer in a kev file  
HP I don't see this with the same build - could you send me the logfile?

Hans-Peter Reicher wrote:
> already posted this weeks ago, but nobody replied.
> so after installing the latest build 200802041024 - I tried adain,  but 
> sill ...
> 
> The shown time of an event in the "Trace Log" view starts with zero on 
> every new tracebuffer.
> see here:
> Event, Time, Owner, Type, Data
> 293815, 999ms 995us, MMI3GApplication (77854) Thread 7 (7), SyncSemPost 
> Enter, sync_ptr 0x803aa2c count 0 owner 0xfffffffc
> 
> 293816, , MMI3GApplication (77854) Thread 14 (14), Ready, pid 77854 tid 
> 14 priority 15 policy 2
> 293817, 2us, MMI3GApplication (77854) Thread 7 (7), SyncSemPost Exit, 
> ret_val 0x0
> 
> this is not very handy, 'cause you can't use this information anymore
> and using "Real Time" instead is not really an option.
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post4821
> 

-- 
cburgess@qnx.com
Re: reported event time (re)starts with zero on every new tracebuffer in a kev file  
Ok, I do see it in this log!

I don't think it's every buffer - rather, it's every 1 seconds, the time shown
flips from 999ms to 0!

However the cycle counts logged in the trace looks just fine,  so I'm stumped
right now.

Hans-Peter Reicher wrote:
> already posted this weeks ago, but nobody replied.
> so after installing the latest build 200802041024 - I tried adain,  but 
> sill ...
> 
> The shown time of an event in the "Trace Log" view starts with zero on 
> every new tracebuffer.
> see here:
> Event, Time, Owner, Type, Data
> 293815, 999ms 995us, MMI3GApplication (77854) Thread 7 (7), SyncSemPost 
> Enter, sync_ptr 0x803aa2c count 0 owner 0xfffffffc
> 
> 293816, , MMI3GApplication (77854) Thread 14 (14), Ready, pid 77854 tid 
> 14 priority 15 policy 2
> 293817, 2us, MMI3GApplication (77854) Thread 7 (7), SyncSemPost Exit, 
> ret_val 0x0
> 
> this is not very handy, 'cause you can't use this information anymore
> and using "Real Time" instead is not really an option.
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post4821
> 

-- 
cburgess@qnx.com
Re: reported event time (re)starts with zero on every new tracebuffer  
No change on this issue with
   Build id: I20080227
just tested this.
Is there PR filed for this?
/hp
Re: reported event time (re)starts with zero on every new tracebuffer  
Please report a problem through your customer support channel.
Re: reported event time (re)starts with zero on every new tracebuffer  
just imagine that I am doing this testing as a private person, not in my function as an employee.
So why should I have to file a PR (I can't do this as a private one) for something very obvious and something that 
aleady is proved by Colin.
Colin also reported to me that after alerting him, he now sees this problem in other logs too - so it's a problem in 
general, not a special problem to me
thanks
hp
Re: reported event time (re)starts with zero on every new tracebuffer  
On Tue, Mar 4, 2008 at 2:48 AM, Hans-Peter Reicher <
hpreichert@harmanbecker.com> wrote:

> just imagine that I am doing this testing as a private person, not in my
> function as an employee.


... but you aren't =;-)

As a general comment.  The forums are not a replacement for the QNX support
services.  They
enhance the services and provide a direct connection to QNX developers, both
those employed
by QNX and those working with QNX for their own purposes.

If you want to ensure that something is fixed and addressed for your
organization, then using
your support contract is the way to go.


> So why should I have to file a PR (I can't do this as a private one) for
> something very obvious and something that aleady is proved by Colin.
> Colin also reported to me that after alerting him, he now sees this
> problem in other logs too - so it's a problem in general, not a special
> problem to me
>
... but it is important to you and your organization, so you should ensure
that the report gets
filed by your organization.  Otherwise it may be seen as an internal report
and not get the visibility
it would normally get as a customer reported PR during problem report
triages.  We are attempting
to ensure that customer reported issues get first use of developers time ...
and in the future you
will also be able to more closely track the progress of PR's that you have
filed.

That is why it is important for you to ensure that a PR is filed with your
name/organization attached
to it (whether this is done by Colin or not is a different matter all
together).

Thomas
RE: reported event time (re)starts with zero on every new tracebu ffer  
Thomas, do you know why it works in 4.0.1? Did you make this special
re-ordering events hack in IDE? Why it stopped working now?
Re: reported event time (re)starts with zero on every new tracebu ffer  
On Tue, Mar 4, 2008 at 11:13 AM, Elena Laskavaia <elaskavaia@qnx.com> wrote:

> Thomas, do you know why it works in 4.0.1? Did you make this special
> re-ordering events hack in IDE? Why it stopped working now?


I _believe_ it has to do with the fact that 6.3.2 logs put the buffer event
out before
the time event.

The IDE fix would likely be in the normalizing code, I'm looking at it now
pending Colin giving me some more information.

Thanks,
 Thomas
Re: reported event time (re)starts with zero on every new tracebuffer  
I'm working on a plug-in for the SystemProfiler right now and I have the same problem as posted by HP Reichert.

The following code snippet behaves exactly the same way HP Reichert described:

...
   final long totalNano = TraceUtil.cycle2ns(cycle, eProv, true);
   return TimeFmt.toString(totalNano, TimeFmt.DISPLAY_MILLI |
      TimeFmt.DISPLAY_MICRO);
}

I don't know whether the data used for conversion has changed or the conversion algorithm itself. However, I think that 
the TraceUtil.cycle2ns(...) method returns the wrong value.

I hope that helps a bit.

Greetings

Slawa
Re: reported event time (re)starts with zero on every new tracebu ffer  
We found a bug in format class and fixed it. Which version you are using?

Wjatscheslaw Talanow wrote: 

I'm working on a plug-in for the SystemProfiler right now and I have the
same problem as posted by HP Reichert. 

The following code snippet behaves exactly the same way HP Reichert
described: 

... 
   final long totalNano = TraceUtil.cycle2ns(cycle, eProv, true); 
   return TimeFmt.toString(totalNano, TimeFmt.DISPLAY_MILLI | 
      TimeFmt.DISPLAY_MICRO); 
} 

I don't know whether the data used for conversion has changed or the
conversion algorithm itself. However, I think that the
TraceUtil.cycle2ns(...) method returns the wrong value.

I hope that helps a bit. 

Greetings 

Slawa 

_______________________________________________ 
General 
http://community.qnx.com/sf/go/post6232
<http://community.qnx.com/sf/go/post6232>;  
Re: reported event time (re)starts with zero on every new tracebuffer  
On Fri, Mar 28, 2008 at 4:56 AM, Wjatscheslaw Talanow <
wtalanow@harmanbecker.com> wrote:

> I'm working on a plug-in for the SystemProfiler right now and I have the
> same problem as posted by HP Reichert.
>
> The following code snippet behaves exactly the same way HP Reichert
> described:
>
> ...
>   final long totalNano = TraceUtil.cycle2ns(cycle, eProv, true);
>   return TimeFmt.toString(totalNano, TimeFmt.DISPLAY_MILLI |
>      TimeFmt.DISPLAY_MICRO);
> }
>
> I don't know whether the data used for conversion has changed or the
> conversion algorithm itself. However, I think that the TraceUtil.cycle2ns(...)
> method returns the wrong value.
>
Hey Slawa, how's it going?

.... well since you are using totally undocumented API .. things are
definitely subject to change =;-)

In this case I suspect that the problem is not the cycle2ns() call ..
although with the next IDE release,
you should be using a different method since timebases on
ITraceEventProviders can be offset, in this
case it doesn't matter since you are normalizing the time against the start
of the log (what the 'true'
is doing in the TraceUtil.cycle2ns() call).

You are likely being bitten by the fact that TimeFmt was more or less doing
whatever it wanted to format
the string .. so if you had seconds included in your time (as well as MS and
US) then it would just not
show them.  This has been fixed and should show up in the next integration
build.

Hope this helps, sorry I can't be more specific .... I don't work for QNX
any more, so I'll let someone
else comment on the timelines for those integration builds (... hint hint
... it would be great to have
a build schedule QNX IDE guys =;-)

Thomas
AW: reported event time (re)starts with zero on every new tracebuffer  
it should work now, since with Build id: I20080313
event times are reported including [s] part in Timelog View.

MoVE's still moving ...
... but we are already using it.

hp


-----Ursprüngliche Nachricht-----
Von:	Thomas Fletcher [mailto:tfletche@gmail.com]
Gesendet:	Sa 29.03.2008 01:59
An:	general-ide
Cc:	
Betreff:	Re: reported event time (re)starts with zero on every new tracebuffer

On Fri, Mar 28, 2008 at 4:56 AM, Wjatscheslaw Talanow <
wtalanow@harmanbecker.com> wrote:

> I'm working on a plug-in for the SystemProfiler right now and I have the
> same problem as posted by HP Reichert.
>
> The following code snippet behaves exactly the same way HP Reichert
> described:
>
> ...
>   final long totalNano = TraceUtil.cycle2ns(cycle, eProv, true);
>   return TimeFmt.toString(totalNano, TimeFmt.DISPLAY_MILLI |
>      TimeFmt.DISPLAY_MICRO);
> }
>
> I don't know whether the data used for conversion has changed or the
> conversion algorithm itself. However, I think that the TraceUtil.cycle2ns(...)
> method returns the wrong value.
>
Hey Slawa, how's it going?

.... well since you are using totally undocumented API .. things are
definitely subject to change =;-)

In this case I suspect that the problem is not the cycle2ns() call ..
although with the next IDE release,
you should be using a different method since timebases on
ITraceEventProviders can be offset, in this
case it doesn't matter since you are normalizing the time against the start
of the log (what the 'true'
is doing in the TraceUtil.cycle2ns() call).

You are likely being bitten by the fact that TimeFmt was more or less doing
whatever it wanted to format
the string .. so if you had seconds included in your time (as well as MS and
US) then it would just not
show them.  This has been fixed and should show up in the next integration
build.

Hope this helps, sorry I can't be more specific .... I don't work for QNX
any more, so I'll let someone
else comment on the timelines for those integration builds (... hint hint
... it would be great to have
a build schedule QNX IDE guys =;-)

Thomas


_______________________________________________
General
http://community.qnx.com/sf/go/post6266 
 
*******************************************
Harman Becker Automotive Systems GmbH
Geschaeftsfuehrung:  Dr. Wolfgang Ptacek  -  Michael Mauser  -  Regis Baudot
Sitz der Gesellschaft: Karlsbad - Registergericht: Mannheim HRB 361395
 
*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat 
sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail
. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have 
received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, 
disclosure or distribution of the contents in this e-mail is strictly forbidden.
*******************************************
Attachment: Text winmail.dat 4.54 KB
Re: AW: reported event time (re)starts with zero on every new tracebuffer  
Hey Thomas,

glad to hear you're still around! Well, things are moving forwards and I'm almost done with my studies. How about you?

As for the bug, looks like it has been fixed in the build I20080313 (as reported by HP). But I still have to use time 
normalization since the MoVE Log output has to be in sync with the SystemProfiler's Event Log.

I only wished I had a really nice API documentation for the SystemProfiler's Core and UI as well as for the 
communication between SystemProfiler's UI components to synchronize SystemProfiler' with MoVE ;)

Greetings

Slawa