Hi,
[quote user="DARAM"]
even if i try to look in to dis-assembly window what can i look in to exactly to understand the situation,is there any way to check out my current stack size ?
[/quote]
As I mentioned before, the disassembly allows you to inspect in detail the instructions and the register values (including the stack pointer) when the function preprocess_analysis() is about to return. If any suspicious code (a MOV operation that overwrites an invalid location, for example) or any invalid values are being passed to certain registers, you can tell precisely where this is happening.
There is no functionality to check the remaining stack or heap available, but this thread points to some useful documents that can help you.
[quote user="DARAM"]
in the above file the .myheap is different from heap,when i am saying -heap <size> which memory location will be allocated for heap ?
kindly note that i am not at all using any sort of malloc in my code i am using a custom malloc which will allocate the memory from .myheap ! so from this its clear that i am not facing this problem because of heap size ? ! but why this not resolved even if the stack size is greatly increased ?
[/quote]
The -heap linker option stores the heap in the .sysmem memory section. However, since you are using your own allocator, this section will not be used.
I will address the rest of the topics at a later post.
Regards,
Rafael