- 
    Type:
Bug
 - 
    Resolution: Done
 - 
    Priority:
Major - P3
 - 
    Affects Version/s: 2.4.0-rc2
 - 
    Component/s: JavaScript, Shell
 - 
    None
 
- 
        Fully Compatible
 - 
        ALL
 - 
        None
 
- 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 - 
        None
 
For version 2.4.0-rc0, we had mimicked the error reporting from version 2.2.
MongoDB shell version: 2.2.4-pre-
> var v = foo.bar.baz;
Sat Mar 09 14:16:35 ReferenceError: foo is not defined (shell):1
MongoDB shell version: 2.4.0-rc0
> interpreterVersion()
V8 3.12.19
> var v = foo.bar.baz;
Sat Mar 09 14:51:40.597 ReferenceError: foo is not defined (shell):1
In version 2.4.0-rc2, we are getting extra text that seems unnecessary:
MongoDB shell version: 2.4.0-rc2
> interpreterVersion()
V8 3.12.19
> var v = foo.bar.baz;
Sat Mar 09 15:02:25.723 JavaScript execution failed: ReferenceError: foo is not defined
We also lost the "(shell):1" text, but that might be consider a "feature".
It would be nice to get rid of the "JavaScript execution failed: " text.
Also, commit https://github.com/mongodb/mongo/commit/f11d2b67e2f185a0934d76cca21361b0679e5301 added an "L" before the line number, which does not match prior error logging.
- is related to
 - 
                    
SERVER-8553 Prevent use of v8 state after error condition
-         
 - Closed
 
 -         
 - 
                    
SERVER-8292 Make JavaScript error reporting more closely match version 2.2
-         
 - Closed
 
 -         
 - 
                    
SERVER-8618 Add context to JavaScript errors reported by v8
-         
 - Closed
 
 -