On 19/3/2022 8:29 pm, Sebastian Huber wrote:
> On 19/03/2022 08:31, Chris Johns wrote:
>>> On 15 Mar 2022, at 5:27 pm, Sebastian
>>> Huber wrote:
>>>
>>> The rtems_shell_init() passed the address of a stack variable
>>> (exit_code) to rtems_shell_run(). If wait == false, then the stack
>>> varia
On 19/03/2022 08:31, Chris Johns wrote:
On 15 Mar 2022, at 5:27 pm, Sebastian Huber
wrote:
The rtems_shell_init() passed the address of a stack variable
(exit_code) to rtems_shell_run(). If wait == false, then the stack
variable goes out of scope but may be accessed by the created shell
thre
> On 15 Mar 2022, at 5:27 pm, Sebastian Huber
> wrote:
>
> The rtems_shell_init() passed the address of a stack variable
> (exit_code) to rtems_shell_run(). If wait == false, then the stack
> variable goes out of scope but may be accessed by the created shell
> thread.
>
> The rtems_shell_sc
The rtems_shell_init() passed the address of a stack variable
(exit_code) to rtems_shell_run(). If wait == false, then the stack
variable goes out of scope but may be accessed by the created shell
thread.
The rtems_shell_script() was affected by the same problem.
Close #4629.
---
cpukit/libmisc
