Skip to content

Reported error has no details when script loading fails #42

@bghgary

Description

@bghgary

When loading a script, if the loading fails due to a parse error or some other error, the error output is not detailed enough to determine what is wrong. Here is an example when running Chakra:

Microsoft C++ exception: UnifiedRegex::ParseError at memory location 0x0000005DEC96B6B0.
Microsoft C++ exception: ParseExceptionObject at memory location 0x0000005DEC968ED0.
Uncaught Error: Unknown failure

It is possible to figure out the problem by stopping at the first exception, but it would be much better if the error message included the line number and what failed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions