[solved] Redirecting Console Output to a File.

geekinthesticks · 2014-02-26 09:05:14

I am having a problem with an extension that locks up Chromium. In the hope of getting some debugging information I am starting chromium from a terminal and redirecting output to a file:

chromium > chromium.log

However, nothing is appended to the file. I am using zsh if that makes a difference.

Last edited by geekinthesticks (2014-03-03 08:55:46)

tomk · 2014-02-26 09:11:51

Maybe there's no output - if you run it without redirection, do you see anything?

geekinthesticks · 2014-02-26 09:20:26

Yes, I see lots of output if I don't try and redirect it to a file.

karol · 2014-02-26 09:25:07

How do you know nothing is written to the file?
Did you open the file while chromium was still running?

geekinthesticks · 2014-02-26 09:26:26

I have looked at the file both while Chromium is running and after closing it normally using the Close button.

karol · 2014-02-26 09:56:53

I'm not using chromium, but I gave it a go just now and it wasn't very talkative. The few lines I got went either to stdout or to stderr. If you redirected stdout to a file you would still get stderr in the terminal.

Awebb · 2014-02-26 09:58:44

Maybe chromium uses STDERR for errors and STDOUT for normal messages.

EDIT: karol, the time traveler!

Last edited by Awebb (2014-02-26 09:59:52)

chaonaut · 2014-02-26 10:52:29

geekinthesticks wrote:

In the hope of getting some debugging information I am starting chromium from a terminal and redirecting output to a file:
chromium > chromium.log

you should redirect stderr to a file, since chromium does not do any stdout to console:

chromium 2> chromium.log

geekinthesticks · 2014-02-26 12:23:01

Thanks I tried that, but didn't get any output when Chromium crashed. I am using the Pushbullet extension, which I find very useful. It does log its activity. However, the log is only accessible from within the app. Unfortunately, it causes Chromium to lock up completely and only killall will close it, so I don't get to see Pushbullet's logs.

chaonaut · 2014-02-26 13:51:59

try

chromium 2>&1 | tee chromium.log

geekinthesticks · 2014-03-03 08:55:22

Thanks for the suggestions, but none of them resulted in me getting anything written to the output file. However, I am marking this as closed, as it appears to be a Chromium bug, rather than the extension. After upgrading to Version 35.0.1862.0 aura (253683) the lock ups have stopped.

Arch Linux

#1 2014-02-26 09:05:14

[solved] Redirecting Console Output to a File.

#2 2014-02-26 09:11:51

Re: [solved] Redirecting Console Output to a File.

#3 2014-02-26 09:20:26

Re: [solved] Redirecting Console Output to a File.

#4 2014-02-26 09:25:07

Re: [solved] Redirecting Console Output to a File.

#5 2014-02-26 09:26:26

Re: [solved] Redirecting Console Output to a File.

#6 2014-02-26 09:56:53

Re: [solved] Redirecting Console Output to a File.

#7 2014-02-26 09:58:44

Re: [solved] Redirecting Console Output to a File.

#8 2014-02-26 10:52:29

Re: [solved] Redirecting Console Output to a File.

#9 2014-02-26 12:23:01

Re: [solved] Redirecting Console Output to a File.

#10 2014-02-26 13:51:59

Re: [solved] Redirecting Console Output to a File.

#11 2014-03-03 08:55:22

Re: [solved] Redirecting Console Output to a File.

Board footer