WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
75605
WTF logging functions should call vprintf_stderr_common only once per line
https://bugs.webkit.org/show_bug.cgi?id=75605
Summary
WTF logging functions should call vprintf_stderr_common only once per line
Mark Rowe (bdash)
Reported
2012-01-04 23:59:34 PST
Currently several of the WTF logging functions make multiple calls to vprintf_stderr_common to output a single line of text. This results in strangely formatted output if vprintf_stderr_common is retargeted to an output device such as syslog that is message-oriented rather than stream-oriented.
Attachments
Patch v1
(8.29 KB, patch)
2012-01-05 00:10 PST
,
Mark Rowe (bdash)
mitz: review+
webkit-ews
: commit-queue-
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Mark Rowe (bdash)
Comment 1
2012-01-05 00:10:23 PST
Created
attachment 121227
[details]
Patch v1
WebKit Review Bot
Comment 2
2012-01-05 00:12:45 PST
Attachment 121227
[details]
did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/JavaScriptCore/ChangeLog', u'Source..." exit_code: 1 Source/JavaScriptCore/wtf/Assertions.cpp:130: vprintf_stderr_with_prefix is incorrectly named. Don't use underscores in your identifier names. [readability/naming] [4] Source/JavaScriptCore/wtf/Assertions.cpp:139: vprintf_stderr_with_trailing_line is incorrectly named. Don't use underscores in your identifier names. [readability/naming] [4] Total errors found: 2 in 2 files If any of these errors are false positives, please file a bug against check-webkit-style.
mitz
Comment 3
2012-01-05 00:21:42 PST
Comment on
attachment 121227
[details]
Patch v1 View in context:
https://bugs.webkit.org/attachment.cgi?id=121227&action=review
> Source/JavaScriptCore/wtf/Assertions.cpp:134 > + strcat(formatWithPrefix.get(), format);
This is effectively strlen()ing prefix again. You could have done this a little more efficiently.
Early Warning System Bot
Comment 4
2012-01-05 00:23:06 PST
Comment on
attachment 121227
[details]
Patch v1
Attachment 121227
[details]
did not pass qt-ews (qt): Output:
http://queues.webkit.org/results/11128164
Mark Rowe (bdash)
Comment 5
2012-01-05 01:16:56 PST
Landed in
r104124
.
Csaba Osztrogonác
Comment 6
2012-01-05 02:40:20 PST
Comment on
attachment 121227
[details]
Patch v1 View in context:
https://bugs.webkit.org/attachment.cgi?id=121227&action=review
> Source/JavaScriptCore/wtf/Assertions.cpp:128 > +#if COMPILER(GCC) > +#pragma GCC diagnostic push > +#pragma GCC diagnostic ignored "-Wformat-nonliteral" > +#endif
This change is absolutely incorrect, because push introduced in gcc 4.6. We can't expect that everyone use this gcc. We should use this pragma inside a similar guard: #if defined(__GNUC__) && (__GNUC__ * 100 + __GNUC_MINOR__ >= 406) ... #endif
Csaba Osztrogonác
Comment 7
2012-01-05 02:42:02 PST
GCC_VERSION_AT_LEAST(4, 6, 0) is better.
Mark Rowe (bdash)
Comment 8
2012-01-05 02:42:47 PST
That would probably prevent it from being picked up by clang.
Mark Rowe (bdash)
Comment 9
2012-01-05 02:47:21 PST
I'd guess that something like the following would do the trick: #if COMPILER(CLANG) || (COMPILER(GCC) && GCC_VERSION_AT_LEAST(4, 6, 0)) I have no way to test it with GCC though.
Zoltan Herczeg
Comment 10
2012-01-05 03:08:26 PST
(In reply to
comment #9
)
> I'd guess that something like the following would do the trick: > > #if COMPILER(CLANG) || (COMPILER(GCC) && GCC_VERSION_AT_LEAST(4, 6, 0)) > > I have no way to test it with GCC though.
I have already landed
http://trac.webkit.org/changeset/104134
. Shall I add the CLANG test?
Mark Rowe (bdash)
Comment 11
2012-01-05 03:17:49 PST
Given that your change broke all of the Mac builds, please do.
Zoltan Herczeg
Comment 12
2012-01-05 04:19:55 PST
(In reply to
comment #11
)
> Given that your change broke all of the Mac builds, please do.
Sorry for that. Buildfix landed.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug