Opened on 10/12/20 at 13:21:05
Last modified on 11/09/22 at 22:32:58
#4144 new defect
fileio - Stack too small for login with password (cloned)
Reported by: | Frank Kuehndel | Owned by: | joel@… |
---|---|---|---|
Priority: | normal | Milestone: | Indefinite |
Component: | test | Version: | 5 |
Severity: | minor | Keywords: | fileio, stack, password, login, root |
Cc: | Blocked By: | ||
Blocking: |
Description
Cloned from #4143:
When I use the 'shell' from the fileio sample with the command below:
env QEMU_AUDIO_DRV="none" \ qemu-system-arm -no-reboot -net none -nographic -M realview-pbx-a9 -m 256M \ -kernel build/arm/realview_pbx_a9_qemu/testsuites/samples/fileio.exe
The executable crashes with an "BLOWN STACK!!!" as soon as I try to login
as 'root' with password. (The logins without password work fine.) Increasing
the stack size of the affected thread a bit (to 5 times RTEMS_MINIMUM_STACK_SIZE) solves the issue.
How to reproduce:
- Start the fileio sample in QEMU with the above command.
- Type a key to stop the timer.
- Type "s" <return> to enter the shell.
- Login as "root" with the password printed to the terminal.
- In the line with the first shell prompt, the text "BLOWN STACK!!!" appears unexpectedly followed by further crash information.
[...] /dev/foobar login: root Password: RTEMS Shell on /dev/foobar. Use 'help' to list commands. SHLL [/] # BLOWN STACK!!! task control block: 0x00205278 [...]
Change History (2)
comment:1 Changed on 10/12/20 at 13:27:26 by Joel Sherrill
comment:2 Changed on 11/09/22 at 22:32:58 by Chris Johns
Milestone: | 5.2 → Indefinite |
---|
Note: See
TracTickets for help on using
tickets.
At the risk of repeating myself, why do we ever use -O0 anymore now that GCC has -Og. From https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
I don't have problem with increasing the configured minimum stack size value for this sample. It would be better than tinkering with individual create invocations. But if -O0 is the culprit, let's just switch away from it.