dave carlson(deleted)
|
Re: continuing problems with user events "data" in profiler
|
dave carlson(deleted)
06/01/2011 9:24 AM
post86324
|
Re: continuing problems with user events "data" in profiler
That log (which terminated my post), is for exactly this from traceprint.
NOTE that the traceprint (ie., the kev) sees exactly the string/data pairs I sent.
NOTE that the ide jpg shows the "data" half as "strings" for event Id 21 even though eventId 7 and 20 *which are making
the same call* are correctly "data".
NOTE: the profiler has had this problem since 4.0.1.
Please help.
t:0x9a8c6d65 CPU:00 KER_EXIT:MSG_SENDV/11 status:84 rmsg:"" (0x00000000)
t:0x9a8c6f2d CPU:00 USREVENT:EVENT:7 STR:"IpcMsgSender"
t:0x9a8c7005 CPU:00 USREVENT:EVENT:7, d0:0x00003ba5 d1:0x0000018c
t:0x9a8c741e CPU:00 KER_CALL:SYNC_SEM_WAIT/85 sync_p:0x510668 count:0
t:0x9a8c74dd CPU:00 THREAD :THSEM pid:45080 tid:10
t:0x9a8c7573 CPU:00 THREAD :THRUNNING pid:45080 tid:19
t:0x9a8c7731 CPU:00 KER_EXIT:SYNC_CONDVAR_WAIT/82 ret_val:0 empty:0x00000000
t:0x9a8c7b6c CPU:00 USREVENT:EVENT:21 STR:"llcs Timer Regular"
t:0x9a8c7c73 CPU:00 USREVENT:EVENT:21, d0:0x00000000 d1:0x00000000
t:0x9a8c9605 CPU:00 USREVENT:EVENT:21 STR:"anet_q dequeue"
t:0x9a8c9763 CPU:00 USREVENT:EVENT:21, d0:0x00000031 d1:0x00000000
t:0x9a8c9bf3 CPU:00 USREVENT:EVENT:20 STR:"AOS ReceiveMsg"
t:0x9a8c9cdd CPU:00 USREVENT:EVENT:20, d0:0x00000002 d1:0x00000001
t:0x9a8c9e59 CPU:00 INT_ENTR:0x0000001a (26) IP:0x0040b458
t:0x9a8c9ef2 CPU:00 INT_HANDLER_ENTR:0x0000001a (26) PID:1 IP:0xfe042f74 AREA:0x00000000
t:0x9a8ca119 CPU:00 INT_HANDLER_EXIT:0x0000001a (26) SIGEVENT:INTR EVENT
t:0x9a8ca1b5 CPU:00 INT_EXIT:0x0000001a (26) inkernel:0x00000001
t:0x9a8ca43b CPU:00 USREVENT:EVENT:20 STR:"AOS eventqueue"
t:0x9a8ca532 CPU:00 USREVENT:EVENT:20, d0:0x00000002 d1:0x00000001
|
|
|