[MXS-251] Non-thread safe strerror Created: 2015-07-07 Updated: 2015-09-06 Resolved: 2015-09-06 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 1.2.0 |
| Fix Version/s: | 1.3.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | martin brampton (Inactive) | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
All |
||
| Description |
|
The non-thread safe function strerror is used at many points in MaxScale. The thread safe version strerror_r is used in a few places. Although the fact that it is obviously only used in error handling situations, it is still quite possible that such events will occur as a cluster and the lack of thread safety will cause poor diagnostic output and unpredictable behaviour. |
| Comments |
| Comment by Massimiliano Pinto (Inactive) [ 2015-08-24 ] |
|
Added strerror_r in binlog router, 1.2.1-binlog_router_trx branch |
| Comment by Johan Wikman [ 2015-09-06 ] |
|
All strerrors changed into strerror_r everywhere BUT in binlog router. |