[SERVER-2808] when we get a seg fault (or similar) signal we should print the faulting address Created: 21/Mar/11 Updated: 12/Jul/16 Resolved: 24/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.8.1, 1.9.0 |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
This can be helpful for debugging. There are a few different addresses that can be accessed from metadata, but I think the memory location that was referenced to cause the seg fault may be most helpful. There may not be a cross platform way to get this info, so may want to just implement on linux. |
| Comments |
| Comment by auto [ 24/Mar/11 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by auto [ 24/Mar/11 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by auto [ 24/Mar/11 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by auto [ 24/Mar/11 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |