application deployed on vxWorks, incorrect argument passed on frame on
From
kanika1406suri@gmail.com@21:1/5 to
All on Fri Mar 29 06:02:46 2019
In my application which is deployed on vxWorks following backtrace (generated on xrtc file) is generated:
d475c (Frame 1) process_host_invoke+274: d3bac (ffffff00, 3e8)
d3cac (Frame 2) stop_feature_monitor+904: receive_invoke_reply ()
d0318 (Frame 3) receive_invoke_reply+7c : wait_reply_msg (3e8, 7950818, ffffff00)
cc6a4 (Frame 4) wait_reply_msg+98 : semTake (ffffff00, 3e8)
859690 (Frame 5) semTake +28 : vxWorks_semTake (ffffff00, 3e8)
Following are the prototype of methods invoked above:
void process_host_invoke(X *param);
int wait_reply_msg(uchar **msg,int* size,int wait_tick );
STATUS semTake(
SEM_ID semId, /* semaphore ID to take */
int timeout /* timeout in ticks */
);
Is it possible that argument of type uchar **msg from frame 3 is passed on to frame 5 as an argument even when the data types are different.
I am new to vxWorks environment. Is it possible that function arguments are passed incorrectly on stack.
FFFFFF00 (H)--> 4,294,967,040 this value is passed as SEM_ID in semTake I got S_objLib_OBJ_ID_ERROR when semTake is invoked.
PS: I don't have dump file
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)