Updates:
Status: WontFix
Comment #5 on issue 18319 by bre...@chromium.org: A possible(!) Logical bug
in logging.cc (on a rare case)
http://code.google.com/p/chromium/issues/detail?id=18319
The logging system is designed to have some reasonable defaults if you don't
initialize it that will be appropriate for any random toy program you write.
In Chrome, we always initialize it manually in
chrome/common/logging_chrome. This
specifies the chrome::DIR_LOGS directory to put it in, which resolves to the
USER_DATA_DIR.
It's possible code may run before we call InitLogging, but I don't think we
need to
worry about this, especially since it will work for normal developers
(since the
current directory will be writable).
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
