[SERVER-4151] mutexDebugger debugger called without DEV macro Created: 26/Oct/11 Updated: 11/Jul/16 Resolved: 27/Oct/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Travis Dunn | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
release (i think the intent is to only call mutex debugger in debug mode) |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
in the unlock() method in rwlock.h, mutexDebugger.leaving() is called without the "DEV" macro, whereas everywhere else in the code it is in fact called with the DEV macro, presumably to prevent production clutter. Is this intentional? Is there a reason the mutexDebugger is not hidden from production in unlock()? |
| Comments |
| Comment by Travis Dunn [ 27/Oct/11 ] |
|
Excellent! Many thanks, Eliot. |
| Comment by Eliot Horowitz (Inactive) [ 27/Oct/11 ] |
|
this is fixed in 2.0.1 |