[SERVER-7435] Windows stack trace isn't specifying symbol search path Created: 21/Oct/12 Updated: 11/Jul/16 Resolved: 20/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.2.3, 2.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows |
||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | Windows |
| Participants: |
| Description |
|
The Windows version of printStackTrace() isn't specifying a search path for symbol files. The default search path for symbols files (e.g. mongod.pdb) includes the current working directory but does not include the executable directory, so users who run mongod.exe from another directory do not get proper stack traces. Specifying a symbol search path that included the directory where the executable is located would let the code find a .pdb file in that directory. |
| Comments |
| Comment by auto [ 08/Jan/13 ] |
|
Author: {u'date': u'2012-11-13T19:56:39Z', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: Set a symbol search path for Windows stack trace, starting with the |
| Comment by auto [ 20/Nov/12 ] |
|
Author: {u'date': u'2012-11-13T19:56:39Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Set a symbol search path for Windows stack trace, starting with the |