It could be something very basic like stack overflow. In situations like this one I find that the following method of debugging is very productive: - Try to isolate a usage pattern that leads to the bug reliably, so that you can repeat it many times. - Set breakpoints in the code as close to the crash as possible. Start off with breakpoints in working code then move the breakpoints further along the usage pattern. Add some if() statements to the code if you need conditional breakpoints. - Once you've isolated the exact place in the code where it goes astray, it should be easy to find the reason by looking at variables and memory contents.
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
