[SERVER-18781] Work out level of necessary stack trace compatibility Created: 01/Jun/15 Updated: 15/Sep/15 Resolved: 28/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Mira Carey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Platform 6 07/17/15, Platform 8 08/28/15, Platform 7 08/10/15 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
v8 and spidermonkey don't return stack traces the same way. In particular, there's captureStackTrace functionality for user exceptions. Figure out the right thing to do for this |
| Comments |
| Comment by Mira Carey [ 28/Aug/15 ] |
|
After several iterations, stack traces seem have sufficient information for internal use. Closing this as good enough for now. |