message, stack members not found unless manually set about clearscript HOT 8 CLOSED

Version 5.5.3 will include a fix for this.

from clearscript.

Hi @nloewen,

We ran the following C# test code in an attempt to confirm your report:

engine.Script.dump = new Action<dynamic>(arg => {
    Console.WriteLine(arg.message);
    Console.WriteLine(arg.stack);
});

engine.Execute(@"
    dump(new Error('hello'));
    dump({x:1});
");

This code threw no exceptions and produced the expected output:

hello
Error: hello
    at Script Document:2:26
[undefined]
[undefined]

Are you doing something differently? Can you provide a minimal code sample that reproduces the issue?

Thanks!

from clearscript.

The following VB.net code produces the error

Imports Microsoft.ClearScript

Public Module Module1

    Sub Main()
        Dim engine = New V8.V8ScriptEngine()

        engine.Script.dump = Sub(arg As Object)
                                 Console.WriteLine(arg.message)
                                 Console.WriteLine(arg.stack)
                             End Sub

        engine.Execute("dump({message:'hello',stack:'trace'});" & _
                       "dump(new Error('world'));")
    End Sub

End Module

from clearscript.

Hi @nloewen,

We've confirmed your report. The key difference between the two cases is that the message and stack properties of JavaScript error objects are not enumerable.

VB.NET and C# behave very differently when dealing with dynamic objects, and VB.NET appears to have some quirks that sometimes block access to non-enumerable JavaScript properties.

Would you mind trying something? If you reverse the order of the two calls to dump, does the test still fail?

Thanks!

from clearscript.

This works,

engine.Execute("dump(new Error('world'));" & _
               "dump({message:'hello',stack:'trace'});")

As does this

engine.Execute("dump(new Error('world'));" & _
               "dump({message:'hello',stack:'trace'});" & _
               "dump(new Error('world'));")

Thanks for looking into this issue!

from clearscript.

Fixed in Version 5.5.2.

from clearscript.

I've found a case that isn't fixed in 5.5.2

engine.Execute("dump(new Error('test'));" & _
               "dump({message:'test'});")

I would expect the second call to dump to print [undefined] instead of throwing an exception.

from clearscript.

Version 5.5.3 has been posted.

from clearscript.