[SERVER-49679] Dump JS debug information when aborting in the mongo shell Created: 16/Jul/20 Updated: 03/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Shell, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Raiden Worley (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
When an invariant is hit in the mongo shell, it can be hard to figure out from the core dump which JS-side functions called into the native code to trip the invariant, especially since a lot of the function names are optimized out in mozjs. It'd really help to dump this at runtime. This might need some investigating. I'm not sure how feasible it would be to get access to the JS stack at the last second. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |
| Comment by Brooke Miller [ 21/Jul/20 ] |
|
We may be able to get the information that we need through Undo, so we plan to leave this on the Backlog until the Undo project (PM-1849) is wrapped up to re-evaluate this need. |