[SERVER-8292] Make JavaScript error reporting more closely match version 2.2 Created: 23/Jan/13 Updated: 11/Jul/16 Resolved: 25/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | 2.4.0-rc0 |
| 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 | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We have a new set of validity checks in our JavaScript interface code due to the switch from SpiderMonkey to V8, and a different routine for displaying JavaScript exceptions. The output should be made to match version 2.2 more closely than it currently does. The display of the JavaScript code that threw an exception, along with a caret indicating where in the line the exception occurred, is not felt to be helpful. SpiderMonkey:
V8:
|
| Comments |
| Comment by auto [ 26/Jan/13 ] |
|
Author: {u'date': u'2013-01-26T15:25:34Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Use the toString() method of Error (and derived) objects to convert them |
| Comment by auto [ 25/Jan/13 ] |
|
Author: {u'date': u'2013-01-25T21:41:49Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: Audit all handling of C++ and JavaScript exceptions in V8 interface code. |