segmentation fault debugging
I am using a mips target and in a certain test scenario, the target crashes with either a segv or a sigbus. I used a gdbserver along with a Insight gui for debugging. In case of sigbus, the insight shows a perfectly legal call stack and i dont see any issue with the last call invoked. However, in case of a segv, the call trace is a junk with some invalid addresses. I am sure that these addresses are completely invalid. I am not getting any break through with this debugging.
All suggestions to approach this issue are welcome.
Last edited by prakash_m80; 03-20-2009 at 04:08 AM.
Reason: wrong section. sud have posted in software section