Timeline for Writing output to file, similar to "script" command?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2016 at 2:35 | comment | added | Julie Pelletier | What is surprising is that you don't get that error when running in the foreground. Can you show your code? | |
| May 14, 2016 at 2:35 | comment | added | Julie Pelletier | That's normal because the buffer gets flushed because of the crash. | |
| May 14, 2016 at 2:31 | comment | added | Guest | The error is: "Program received signal SIGSEGV: Segmentation fault - invalid memory reference." The program quits after this error occurs and it's okay. But knowing the output before it reaches this error helps me remove the data that causes this problem. | |
| May 14, 2016 at 2:12 | comment | added | Julie Pelletier | What's the error message? (wondering if it could be linked to redirection) | |
| May 14, 2016 at 1:37 | comment | added | Guest | Strange, it does produce an output before the error when I write it to screen in the terminal. Maybe I will try it again. | |
| May 14, 2016 at 1:14 | comment | added | Julie Pelletier | Well if you get an empty output, it means that the program produced no output. Since it gave you an error, it probably got the error before outputting anything. | |
| May 14, 2016 at 1:08 | comment | added | Guest | For some reason I still get an empty output.txt file but the error does write to error.txt. I tried doing ./MyProgram.exe >>& output.txt & but received a syntax error. I'm not sure why. | |
| May 13, 2016 at 23:02 | history | answered | Julie Pelletier | CC BY-SA 3.0 |