Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - SystemProfiler - wrong data interpretation of "TimerTimeout Enter": (3 Items)
   
SystemProfiler - wrong data interpretation of "TimerTimeout Enter"  
looks like this is a bug that's in there for a long time now, nobody has seen it.
When looking at events of type "TimerTimeout Enter" in wide mode traces you'll see that there's a field missing and the 
following other fields are shifted.
I take the event definition from the SAT doc:
TimerTimeout()
	A1: id,
	A2: timeout_flags,
	A3: ntime(sec),
	A4: ntime(nsec),
	A5: event->sigev_notify,
	A6: event->sigev_notify_function_p,
	A7: event->sigev_value,
	A8: event->sigev_notify_attributes_p 
RawEvent Data is:
	0x00 0x00 0x00 0x00
	0x00 0x10 0x00 0x00
	0x00 0x00 0x00 0x00
	0x40 0x4B 0x4C 0x00
	0x00 0x00 0x00 0x00
	0x00 0x00 0x00 0x00
	0x00 0x00 0x00 0x00
	0x00 0x00 0x00 0x00
The IDE is reporting:
TimerTimeout Enter, id 0 timeout_flags 0x1000 ntime(sec) 0 event->sigev_notify 5000000 event->sigev_notify_ptr 0x0 event
->sigev_value 0x0 event->sigev_notify_attributes_ptr 0x0

You see that the field "A4: ntime(nsec)" is missing and that the other fields are shifted which leads to wrong values.

/hp

Re: SystemProfiler - wrong data interpretation of "TimerTimeout Enter"  
any pros or cons to this issue?
/hp
Re: SystemProfiler - wrong data interpretation of "TimerTimeout Enter"  
Hans-Peter Reichert wrote:
> any pros or cons to this issue?
>   
Yes .. it is a bug for sure. 

It is (likely) a problem with the manual transcription of the event 
formats from the kernel source code
to the Java world.  The definition string that describes the timer 
timeout event is (probably) missing the
description for the "ntime(nsec)" field.

To save the QNX guys some time finding/verifying that this is the 
problem, the event definition strings are
defined in the utils plugin where all of the kernel calls are defined.

Hope this helps,
 Thomas