View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004081 | DarkRadiant | Design/Coding | public | 07.02.2015 04:40 | 07.01.2016 13:04 |
Reporter | greebo | Assigned To | greebo | ||
Priority | normal | Severity | normal | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 2.0.2 | ||||
Target Version | 2.0.3 | Fixed in Version | 2.0.3 | ||
Summary | 0004081: Make logging subsystem thread-safe | ||||
Description | When offloading existing code (that is often full of rMessage() and rWarning() debug output) to worker threads the logging subsystem needs to be thread-safe. Standard std::ostream-derived classes are not thread-safe themselves, so helper constructs will be needed to achieve that goal. | ||||
Tags | No tags attached. | ||||
This is implemented in the threading branch. All rMessage()/rWarning()/rError() stream accessors are now returning a temporary std::ostringstream-derived object which buffers the message and dispatches it to the application-wide LogStream in a thread-safe manner. The thread lock is kept by the main application and made known to modules in the initialiseStreams() function. | |
Date Modified | Username | Field | Change |
---|---|---|---|
07.02.2015 04:40 | greebo | New Issue | |
07.02.2015 04:41 | greebo | Relationship added | child of 0004080 |
07.02.2015 04:41 | greebo | Assigned To | => greebo |
07.02.2015 04:41 | greebo | Status | new => assigned |
07.02.2015 04:43 | greebo | Note Added: 0007407 | |
15.02.2015 14:39 | greebo | Status | assigned => resolved |
15.02.2015 14:39 | greebo | Fixed in Version | => 2.0.3 |
15.02.2015 14:39 | greebo | Resolution | open => fixed |
07.01.2016 13:04 | greebo | Status | resolved => closed |