PR #1105 should eliminate the primary cause of the error: fs_fdopen() will not longer set the errno variable. The secondary error, the uninitialized stack description, is still a problem.Since the errno value was only set before fs_fdopen() failed, this means that you system will still not work. It should not crash but it should not work either. Now the fs_fdopen() calls will silently and mysteriously fail, perhaps with the only symptom being no standard I/O in the started tasks.
- Arm Kinetis: set_errno in nx_start with CONF... Schock, Johannes - NIVUS GmbH
- RE: Arm Kinetis: set_errno in nx_start ... Schock, Johannes - NIVUS GmbH
- Re: Arm Kinetis: set_errno in nx_start ... Xiang Xiao
- RE: Arm Kinetis: set_errno in nx_st... David Sidrane
- Re: Arm Kinetis: set_errno in n... Xiang Xiao
- RE: Arm Kinetis: set_errno in nx_st... Schock, Johannes - NIVUS GmbH
- Re: Arm Kinetis: set_errno in nx_st... Gregory Nutt
- Re: Arm Kinetis: set_errno in n... Gregory Nutt
- Re: Arm Kinetis: set_errno ... Gregory Nutt
- RE: Arm Kinetis: set_e... Schock, Johannes - NIVUS GmbH
- Re: Arm Kinetis: s... Gregory Nutt
- RE: Arm Kineti... Schock, Johannes - NIVUS GmbH
- Re: Arm Kineti... Gregory Nutt
- RE: Arm Kineti... Schock, Johannes - NIVUS GmbH