Hans-Peter Reichert
|
SystemProfiler - wrong data interpretation of "TimerTimeout Enter"
|
Hans-Peter Reichert
11/10/2008 2:56 AM
post16286
|
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
|
|
|