Sub module's auxiliary stack boundary and bottom may be different from main module's counterpart, so when calling sub module, its aux stack info should be gotten and set to exec_env firstly, or aux stack overflow and out of bounds memory access exception may be thrown when calling sub module's function. Fix the issue reported in PR #1278.