Could it be that you somehow enabled tail call optimization? What happens if you use --no-harmony-tailcalls? If that's not it... we indeed also changed the implementation of stack traces a bit between 4.6 and 5.3. A (preferably reduced) repro would be great to find out what exactly is going on.
Cheers, Yang On Tuesday, November 1, 2016 at 4:19:35 PM UTC+1, Jane Chen wrote: > > Embedding v8 5.3. The embedding application allows JavaScript programs to > import other library modules similar to Node.js require. I noticed a > change of behavior after upgrading from v8 4.6.88 to 5.3. That is, if the > imported library module is in strict mode, the stack trace of a function > call in the library module is collapsed to only have one frame, which is > different from v8 4.6.88 and different from sloppy mode. > > For example, in sloppy mode, a stack trace of: > > at execute (/MarkLogic/optic/optic-amped.sjs:32:17) > at ([anonymous]:3:4) > > becomes: > > at ([anonymous]:3:4) > > We are speculating that maybe strict mode enables optimization which > appears to skip a frame. So my questions are 1) Is this expected? 2) Is > this behavior reliable and going to stay? > > Thanks in advance. > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
