[SERVER-7386] stack traces in v8 don't work Created: 17/Oct/12  Updated: 11/Jul/16  Resolved: 09/Nov/12

Status: Closed
Project: Core Server
Component/s: JavaScript
Affects Version/s: None
Fix Version/s: 2.3.1

Type: Bug 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:
Related
is related to SERVER-2407 Switch to v8 Closed
Operating System: ALL
Participants:

 Description   

Error: Printing Stack Trace
 
	
 
    at <error: TypeError: Object [object builtins] has no method 'FunctionGetInferredName'>
 
	
 
    at <error: TypeError: Object [object builtins] has no method 'FunctionGetInferredName'>
 
	
 
    at <error: TypeError: Object [object builtins] has no method 'FunctionGetInferredName'>
 
	
 
    at <error: TypeError: Object [object builtins] has no method 'FunctionGetInferredName'>
 
	
 
    at startParallelShell (src/mongo/shell/servers_misc.js:283:14)
 
	
 
    at checkYield (jstests/count8.js:24:17)
 
	
 
    at <error: TypeError: Object [object builtins] has no method 'FunctionGetInferredName'>
 
	
 
    at <error: TypeError: Object [object builtins] has no method 'FunctionGetInferredName'>
 
	
 
    at <error: TypeError: Object [object builtins] has no method 'FunctionGetInferredName'>
 
	
 
    at _run (/data/buildslaves/Linux_64bit_v8_Nightly/mongo/jstests/slowNightly/dur_passthrough.js:38:67)

in http://buildlogs.mongodb.org/Nightly%20Linux%2064-bit%20v8/builds/1040/test/recent%20failures/dur_passthrough.js

I see this on the web: https://groups.google.com/forum/?fromgroups=#!topic/v8-dev/b2xEzISQQl0

I'm not sure we have this change in our version of V8.



 Comments   
Comment by auto [ 09/Nov/12 ]

Author:

{u'date': u'2012-11-08T23:05:51Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}

Message: SERVER-7386 Define ENABLE_DEBUGGER_SUPPORT for V8
Branch: master
https://github.com/mongodb/mongo/commit/6fff343f76f0f33d45744d30adf98d7ed1ffcd3d

Comment by Eric Milkie [ 02/Nov/12 ]

I've discovered that defining functions like this:

myfunc = function() {
// etc
}

Causes the error seen above to be printed if the function is in the stack frame.
But if you create a function like this:

function myfunc() {
// etc
}

It all works fine.

Generated at Thu Feb 08 03:14:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.