[SERVER-7087] Investigate exception propagation behavior in V8 Created: 20/Sep/12 Updated: 11/Jul/16 Resolved: 25/Jan/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | JavaScript |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | 2.4.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | 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 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Similar to exception propagation work that was done for SpiderMonkey; ensure that exceptions from callbacks do not adversely affect V8 code. Translate MongoDB C++ exceptions into V8-acceptable JavaScript exceptions. |
| 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. |