WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
Bug 114266
Get rid of truncated thread name warnings for non-Windows platforms
https://bugs.webkit.org/show_bug.cgi?id=114266
Summary
Get rid of truncated thread name warnings for non-Windows platforms
Thiago Marcos P. Santos
Reported
2013-04-09 04:32:07 PDT
ERROR: Thread name "com.apple.WebKit.ProcessLauncher" is longer than 31 characters and will be truncated by Visual Studio /home/buildslave-1/webkit-buildslave/efl-linux-64-debug-wk2/build/Source/WTF/wtf/Threading.cpp(78) : WTF::ThreadIdentifier WTF::createThread(WTF::ThreadFunction, void*, const char*) ERROR: Thread name "com.apple.WebKit.EventDispatcher" is longer than 31 characters and will be truncated by Visual Studio /home/buildslave-1/webkit-buildslave/efl-linux-64-debug-wk2/build/Source/WTF/wtf/Threading.cpp(78) : WTF::ThreadIdentifier WTF::createThread(WTF::ThreadFunction, void*, const char*) ERROR: Thread name "com.apple.WebKit.PluginProcessConnectionManager" is longer than 31 characters and will be truncated by Visual Studio /home/buildslave-1/webkit-buildslave/efl-linux-64-debug-wk2/build/Source/WTF/wtf/Threading.cpp(78) : WTF::ThreadIdentifier WTF::createThread(WTF::ThreadFunction, void*, const char*)
Attachments
Patch
(1.45 KB, patch)
2013-04-09 05:11 PDT
,
Thiago Marcos P. Santos
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Thiago Marcos P. Santos
Comment 1
2013-04-09 05:11:24 PDT
Created
attachment 197032
[details]
Patch
Adam Roben (:aroben)
Comment 2
2013-04-09 05:34:06 PDT
Comment on
attachment 197032
[details]
Patch We had this enabled for all platforms because it seemed likely that long thread names would keep being introduced if the warning only appeared on Windows. But apparently this warning isn't effective. Maybe we should make it a compile-time error instead?
Thiago Marcos P. Santos
Comment 3
2013-04-09 06:51:05 PDT
(In reply to
comment #2
)
> (From update of
attachment 197032
[details]
) > We had this enabled for all platforms because it seemed likely that long thread names would keep being introduced if the warning only appeared on Windows. But apparently this warning isn't effective. Maybe we should make it a compile-time error instead?
Not a Windows expert, but looks to me that you will have a problem only if the truncated names are the same, which doesn't happen today. Maybe is a better idea just keep my patch and file a bug if the collision ever occurs one day.
WebKit Commit Bot
Comment 4
2013-04-10 20:10:49 PDT
Comment on
attachment 197032
[details]
Patch Clearing flags on attachment: 197032 Committed
r148166
: <
http://trac.webkit.org/changeset/148166
>
WebKit Commit Bot
Comment 5
2013-04-10 20:10:51 PDT
All reviewed patches have been landed. Closing bug.
Darin Adler
Comment 6
2013-04-11 10:05:09 PDT
This is unfortunate for code that actually is used on Windows as well as other ports. We’d like to notice that the thread names are no good before actually running on Windows. It seems that the problem comes with code that has no intention of running on Windows, getting warnings about a non-problem. I guess we can just not worry about this any more unless the confusing thread names on Windows become a real world problem for someone, and then we can revisit this.
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