If you can't find any likely source of wild pointers
then you may "just" be blowing your stack. I think there
is stack monitor code for TOS somwplace...try some searching.
You can also try reducing your stack usage by eliminating
functionality, cutting down function call levels (recursion
anyone?) and reducing large automatic variables to see
if it makes any difference. Pay a bit of attention to the
RAM usage reported during the build as well.

MS

Faisal Aslam wrote:
> Hi,
> 
> We have an application that sends packets. It also print the packets on 
> the serial port. There are also some other complex tasks carried out by 
> the application. We have debug that application throughly and found out 
> that TinyOS function CC1000SendReceiveP$listenData somehow overwrites 
> the c-stack. It leads to the application get halt as a return method of 
> a function now points to an invalid address.
> We have checked our code and was not able to find any mistake. Please 
> guide us how can we fix this or give us any ideas?
> Is that errror could be called because of non-atomic regions accessing 
> data? However, we have no asyn functions. What could be the reason of this?
> 
> I will be very thankful with some replies.
> 
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to