Tickprocessor no longer prints error messages on log entries that are unrelated to profiling.

Tickprocessor no longer prints error messages on log entries that are unrelated to profiling.

BUG=v8:1683
Committed: http://code.google.com/p/v8/source/detail?r=9302

[Yang, 2011-09-15 11:47:16]

I think it is unnecessary to print error messages on unknown commands in the log
file because from what I can see, LogReader is only used in the tick processor
and when the log contains more things than necessary for profiling, those things
trigger error messages.

[mnaganov (inactive), 2011-09-15 12:39:29]

Thanks for looking into this!

http://codereview.chromium.org/7906003/diff/1/tools/logreader.js
File tools/logreader.js (left):

http://codereview.chromium.org/7906003/diff/1/tools/logreader.js#oldcode182
tools/logreader.js:182: this.printError('line ' + (this.lineNum_ + 1) + ': ' +
(e.message || e));
Why are you removing this code as well? It's general error handling and it's
usually helps to know the number of an offending line.

[Yang, 2011-09-15 12:52:37]

I restored catching the exceptions. Still omitting the error printing on unknown
command. Please take another look.

[mnaganov (inactive), 2011-09-15 13:11:48]

On 2011/09/15 12:52:37, Yang wrote:
> I restored catching the exceptions. Still omitting the error printing on
unknown
> command. Please take another look.

Thanks! LGTM.