[SERVER-8618] Add context to JavaScript errors reported by v8 Created: 19/Feb/13 Updated: 11/Jul/16 Resolved: 20/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ben Becker | Assignee: | Ben Becker |
| Resolution: | Done | Votes: | 0 |
| Labels: | Javasc, v8 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, JS error messages are very confusing for users; e.g.:
This is partially because we specify an arbitrary variable name (e.g. funcs9) as the script context/filename in V8Scope::_createFunction(). This should either be removed, or toSTLString(v8::TryCatch*) should access the code from the scope's map and parse the start/end position to provide the context reported by v8. |
| Comments |
| Comment by auto [ 20/Feb/13 ] |
|
Author: {u'date': u'2013-02-20T20:12:00Z', u'name': u'Ben Becker', u'email': u'ben.becker@10gen.com'}Message: |
| Comment by auto [ 20/Feb/13 ] |
|
Author: {u'date': u'2013-02-20T17:56:24Z', u'name': u'Ben Becker', u'email': u'ben.becker@10gen.com'}Message: |
| Comment by auto [ 20/Feb/13 ] |
|
Author: {u'date': u'2013-02-20T17:15:46Z', u'name': u'Ben Becker', u'email': u'ben.becker@10gen.com'}Message: |