On Oct 28, 2009, at 5:13 AM, Christoph Baumann wrote:
To check if the environment is messed up in any case, I wrote a simple
program that only dumps the environment variables. This program works
fine. So the cause of the problem lies more in the ssh client.
Has anybody seen similar problems?
What's the stack size of the SSH client?
Remember, the uclinux runtime does not have a dynamic stack size.
Run "<toolchain-prefix>flthdr" on your target FLAT executable to read
the header.
flthdr -s lets you change the stack size. Try increasing the stack size.
Once you find an appropriate size, you can put it into the compile
flags.
Your test program probably didn't need much stack, so it succeeded.
Any time you see improbable values being returned, or crashes on
exiting, or crashes which show the PC being a weird value, suspect
stack corruption - remember, functions return values go on the stack,
as does the return location for function calls. Stack corruption will
often lead to, as we put it, "return to data".
-
allon
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
