[RTEMS Project] #4144: fileio - Stack too small for login with password (cloned)

[RTEMS trac]

#4144: fileio - Stack too small for login with password (cloned)
----------------------------------------------+---------------------
 Reporter:  Frank Kuehndel                    |       Owner:  joel@…
     Type:  defect                            |      Status:  new
 Priority:  normal                            |   Milestone:  5.2
Component:  test                              |     Version:  5
 Severity:  minor                             |  Resolution:
 Keywords:  fileio,stack,password,login,root  |  Blocked By:
 Blocking:                                    |
----------------------------------------------+---------------------

Comment (by Joel Sherrill):

 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

 {{{
 -Og
 Optimize debugging experience. -Og should be the optimization level of
 choice for the standard edit-compile-debug cycle, offering a reasonable
 level of optimization while maintaining fast compilation and a good
 debugging experience. It is a better choice than -O0 for producing
 debuggable code because some compiler passes that collect debug
 information are disabled at -O0.

 Like -O0, -Og completely disables a number of optimization passes so that
 individual options controlling them have no effect. Otherwise -Og enables
 all -O1 optimization flags except for those that may interfere with
 debugging:

 -fbranch-count-reg  -fdelayed-branch
 -fdse  -fif-conversion  -fif-conversion2
 -finline-functions-called-once
 -fmove-loop-invariants  -fssa-phiopt
 -ftree-bit-ccp  -ftree-dse  -ftree-pta  -ftree-sra
 }}}

 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.

--
Ticket URL: <http://devel.rtems.org/ticket/4144#comment:1>
RTEMS Project <http://www.rtems.org/>
RTEMS Project