[Bug fortran/31299] I can produce the bug without using nohup

2007-03-22 Thread michael dot a dot richmond at nasa dot gov
--- Comment #10 from michael dot a dot richmond at nasa dot gov 2007-03-22 13:53 --- Several commenters believe the problem is with nohup rather than gfortran. I can produce the bug without using nohup. I redirect the input to a file: gfortran test_getlog.f90 ./a.out carriage_return

[Bug fortran/31299] I can produce the bug without using nohup

2007-03-22 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2007-03-22 15:19 --- I say GETLOG should have the same behavior as getlogin which is what this behavior is comming from. Considering the documentation says: On systems where the getlogin(3) function is not implemented, this will