VSCode has a group of "Locals" variables, we should add "Member" (this) variables group as well

When I try to debug I got an error "Debug adapter process has terminated unexpectedly".

When using launch request, port variable is disregarded. It supposedly should set debugPort here, but it doesn't:

We don't yet support native debugging on OSX, this library could be helpful in implementing the necessary primitives: https://github.com/blankwall/MacDBG

class Main {
	static function main() {
		var option = haxe.ds.Option.None;
		switch (option) {
			case Some(v):
				trace(v);
			case None:
				trace("");

		}

		trace("");
	}
}

Set a breakpoint on the last line:

v shows up despite being out of scope, with a "Failed to read" error.

When stopping on all exceptions (for instance Eof) - even if caught - resuming the debugger will prevent catching it.

When doing F11 and it involves a C native call, this can take way too long. Still we want to know if there's not a callback to Haxe code.

For an unknown reason the VIdent values of this enum don't show up like the others:

enum CssValue {
   VIdent( i : String );
   VString( s : String );
   VUnit( v : Float, unit : String );
   VFloat( v : Float );
   VInt( v : Int );
   VHex( h : String, v : Int );
   VList( l : Array<CssValue> );
   VGroup( l : Array<CssValue> );
   VCall( f : String, vl : Array<CssValue> );
   VLabel( v : String, val : CssValue );
   VSlash;
   VArray( v : CssValue, ?content : CssValue );
}

When hovering over the string in trace("Test"), I get this confusing message:

Moved from https://github.com/ncannasse/hashlink-debugger/issues/11

I am using Ubuntu 18.10, hl 1.9.0, haxe 4.0.0-rc.2+77068e1, VS Code 1.33.1. When trying to debug Heaps samples for self-teaching reasons I get following error from VS Code:

Could not start hl process, executable was not found in PATH. Restart VSCode or computer.

The build itself works fine. hl is in directory /usr/local/bin and causes no problems using from the command line. VS Code has this path also in the process.env.PATH variable. No idea why hl cannot be launched. Tried also with haxe 4.0.0.-rc1 because it has been mentioned in the documentation that hashlink is compatible with that version, but no difference.

I'm not able to get the Hello Hashlink project (from the Heaps.io getting started site) up and running using this plugin. I am, however, able to run the heaps project starting HL from the command line.

I'm using Windows 10, heaps 1.6.1, haxe 4.0.0-rc.2, hl 1.9 (from pre-built binary).

When using hlsdl, the game window opens, but remains all white (should be black, with white text). Like this:

When choosing hldx, receive an exception on DirectXDriver.hx:

I'm not seeing any problems or errors in the console. Where else can I check for startup issues with this plugin?

Again, the app runs fine when I run from terminal (for example: hl .\hello.hl) when using both hlsdl and hldx specified in the build.hxml file. In both cases, I see this, as expected:

my launch.json is the default:

  {
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "HashLink (launch)",
            "request": "launch",
            "type": "hl",
            "hxml": "build.hxml",
            "cwd": "${workspaceFolder}",
            "preLaunchTask": {
                "type": "haxe",
                "args": "active configuration"
            }
        },
        {
            "name": "HashLink (attach)",
            "request": "attach",
            "port": 6112,
            "type": "hl",
            "hxml": "build.hxml",
            "cwd": "${workspaceFolder}",
            "preLaunchTask": {
                "type": "haxe",
                "args": "active configuration"
            }
        }
    ]
}

Where should I look next?

Code-oss Version 1.33.1
OS: (Void Linux) kernel x64 4.19.38_1

Please let me know if this is the wrong place to post this error.

Using the vscode extension gives this error if a hl process is already running.

ERROR : TypeError: Cannot read property 'stop' of undefined

Called from /home/brandon/.vscode-oss/extensions/haxefoundation.haxe-hl-0.6.0/adapter.js line 6465 column 12
Called from /home/brandon/.vscode-oss/extensions/haxefoundation.haxe-hl-0.6.0/adapter.js line 410 column 12
Called from /home/brandon/.vscode-oss/extensions/haxefoundation.haxe-hl-0.6.0/adapter.js line 356 column 11
Called from events.js line 182 column 13
Called from internal/child_process.js line 961 column 16
Called from stream.socket.on (internal/child_process.js line 380 column 11)
Called from events.js line 182 column 13
Called from _handle.close (net.js line 596 column 12)
Called from module.exports.loopWhile (/home/brandon/.vscode-oss/extensions/haxefoundation.haxe-hl-0.6.0/node_modules/deasync/index.js line 71 column 23)
Called from /home/brandon/.vscode-oss/extensions/haxefoundation.haxe-hl-0.6.0/adapter.js line 13143 column 27

Running hl --debug 6112 <name.hl> will make the process hang until I kill the hl process. When I kill it, I get this output from the hl process.

haxe.Unserializer.unserializeObject(/usr/local/share/haxe/std/haxe/Unserializer.hx:198)
haxe.Unserializer.unserialize(/usr/local/share/haxe/std/haxe/Unserializer.hx:290)
haxe.$Unserializer.run(/usr/local/share/haxe/std/haxe/Unserializer.hx:468)
hxsl.$SharedShader.__constructor__(hxsl/SharedShader.hx:53)
hxsl.Shader.initialize(hxsl/Shader.hx:31)
hxsl.$Shader.__constructor__(hxsl/Shader.hx:14)
h3d.shader.$ScreenShader.__constructor__(h3d/shader/ScreenShader.hx:3)
h3d.shader.$MinMaxShader.__constructor__(h3d/shader/MinMaxShader.hx:3)
h3d.pass.$DirShadowMap.__constructor__(h3d/pass/DirShadowMap.hx:11)
h3d.pass.$DefaultShadowMap.__constructor__(h3d/pass/DefaultShadowMap.hx:16)
h3d.scene.fwd.$Renderer.__constructor__(h3d/scene/fwd/Renderer.hx:61)
h3d.mat.MaterialSetup.createRenderer(h3d/mat/MaterialSetup.hx:16)
h3d.scene.$Scene.__constructor__(h3d/scene/Scene.hx:49)
hxd.App.setup(hxd/App.hx:109)
h3d.Engine.onCreate(h3d/Engine.hx:240)
h3d.impl.GlDriver.~init.0(h3d/impl/GlDriver.hx:1532)
haxe.$Timer.~delay.0(/usr/local/share/haxe/std/haxe/Timer.hx:140)
haxe.$Timer.~__constructor__.0(/usr/local/share/haxe/std/haxe/Timer.hx:74)
haxe.$MainLoop.tick(/usr/local/share/haxe/std/haxe/MainLoop.hx:166)
hxd.$System.runMainLoop(hxd/System.hl.hx:124)
haxe.$Timer.~delay.0(/usr/local/share/haxe/std/haxe/Timer.hx:140)
haxe.$Timer.~__constructor__.0(/usr/local/share/haxe/std/haxe/Timer.hx:74)
haxe.$MainLoop.tick(/usr/local/share/haxe/std/haxe/MainLoop.hx:166)
haxe.$EntryPoint.processEvents(/usr/local/share/haxe/std/haxe/EntryPoint.hx:99)
haxe.$EntryPoint.run(/usr/local/share/haxe/std/haxe/EntryPoint.hx:125)
fun$4292(?:1)
Terminated

Hitting "pause" doesn't work, while it works correctly using HL debugger.
Seems relative to VSCode way to implement it.

class Main {
	public static function main() {
		trace("hello world");
	}
}

Also shows up in the callstack - not sure what that's doing there, since main is the entry point?

Just running a simple hello world heaps project, VSCode launch that exception. launch from terminal using command "hl file.hl" runs with no problem, build is also ok.

i'm using VSCode latest release x64, Haxe 4.0.0-rc.1 (i tried Haxe 4.0.0-preview.5 too) and hashlink 1.9 (tried 1.8 too)

I didn't manage to make "pause" work within VSCode.

It works very well in commandline debugger when doing run 0.5 for example (which will run for 0.5s then pause), so I guess this is something related to the order or callbacks within the HLAdapter.

Summoning @Gama11 for help :)

Currently a HXML file is required by the launch config for classpaths, this should be replaced with a vshaxe API to retrieve the classpaths. See also vshaxe/vshaxe#221.

The reasons for this are that there's not always a HXML file:

• compiler arguments might be in tasks.json only
• it might be a Lime project or some other third-party build tool without hxml

Stepping in switch creates some weird changes in cursor location. To investigate.

Hi! When I attempt to launch the debugger, the debugger gets activated, but no executable is run. After a short while I get a Visual Studio Code prompt saying HandleRequestAsync timeout.

Here's what I have set up on compile.hxml:

-lib heaps
-lib hlsdl
-main Main
-hl hello.hl

/.vscode/launch.json:

{
  "version": "0.2.0",
  "configurations": [   
    {
	"name":    "HashLink",
	"request": "launch",
	"type":    "hl",
	"hxml":    "compile.hxml",
	"cwd":     "${workspaceRoot}",
	"preLaunchTask": {
	  "type" : "haxe",
	  "args" : "active configuration"
	}
    }
  ]
}

/.vscode/tasks.json:

{
  "version": "2.0.0",
  "tasks": [
    {
      "type": "haxe",
      "args": "active configuration",
      "problemMatcher": [
        "$haxe-absolute",
        "$haxe",
        "$haxe-error",
        "$haxe-trace"
      ],
      "group": {
        "kind":      "build",
        "isDefault": true
      }
    }
  ]
}

When I try to run HashLink manually from terminal it runs just fine.

Version/Platform info:

The version of VSCode is 2.0.12
Haxe is 4.0.0-preview.5
HL/JIT 1.9.0
Windows 10

VSHaxe/Hashlink-Debugger: Store versions
Haxe tested: Haxe4-preview4, and latest git (80334fec8).
HL: 1.6.0
OS: Win10 x64
Log:

0> src/HLAdapter.hx:43: initialize
0> src/HLAdapter.hx:59: launch
0> src/HLAdapter.hx:206: start process
0> src/HLAdapter.hx:215: Running: hl --debug-wait --debug 6112 out.hl
0> src/HLAdapter.hx:280: load module
0.2> src/HLAdapter.hx:283: connecting at port 6112
0.2> hack.hx:1: 4:3371
ERROR : Failed to connect on debug port

It never connects to application, instantly saying that it failed to connect (which is false, because it does connect, but receives wrong data). I tinkered with output log for a bit and found that it fails at that point:
https://github.com/HaxeFoundation/hashlink/blob/master/other/debugger/hld/JitInfo.hx#L84-L86
It receives 4 while expecting 3371 (or 3/301 without heaps/hldx). The value seem to be the amount of hdlls loaded, because without hldx library it sends 3.
Minimal reproduction code with Heaps and HLDX (so application would maintain runtime for some time, because it seems to exit very fast with just one trace):
hldebug.zip
It does not connect neither with launch or attach (with manual hl --debug 6112 --debug-wait out.hl) commands.

Even on very simple apps, running them always results in an Access Violation Exception on line 42 of Window.hl.hx. This doesn't seem to be directly a heaps or hashlink problem, because when running on the command line using hl, it works perfectly, so it seems to just be a vscode debugger problem. Running on hl 1.9.0, haxe 4.0.0-preview.5, heaps 1.5.0, hlsdl 1.8.0,
uname -a output: Linux klaptop 4.19.14-1-MANJARO #1 SMP PREEMPT Wed Jan 9 17:17:37 UTC 2019 x86_64 GNU/Linux,
build.hxml looks like this:

-cp src
-main Main
-lib heaps
-lib hlsdl
-hl bin/haxe-testing.hl

This bug happens on any heaps program but here is an example

class Main extends hxd.App {
    override function init() {
        var tf = new h2d.Text(hxd.res.DefaultFont.get(), s2d);
        tf.text = "Hello World !";
    }
    static function main() {
        new Main();
    }
}

Here's the callstack I get when the debugger breaks on the exception:

But this is what I get on the command line:

Shouldn't they match?

Arrays show up as "Unknown variable" in the watch.

Edit:
Sorry... it's working actually but the compiler was optimizing away some statements... is there a way to prevent this (i'm compiling with --debug of course)

• set variable
• attach to process
• choose all exceptions/caught exceptions in breakpoints (see NWJS debugger which allows it)

Hi, i'm beginner to haxe and heaps. I try to debug in vscode, and show this error "Failed to start hl process (Error: spawn hl ENOENT)". Just after i changed electron version to 2.0.9. Before changed electron version i got this error "Debug adapter process has terminated unexpectedly".

Haxe Compiler 4.0.0-preview.5+7eb789f
HL/JIT HL/JIT 1.8.0
HashLink Debugger 0.4.4
VSCode 1.28.2 x64
macOS Mojave

launch.json

  "version": "0.2.0",
  "configurations": [
    {
      "name": "HashLink (launch)",
      "request": "launch",
      "type": "hl",
      "hxml": "compile.hxml",
      "cwd": "${workspaceRoot}",
      "preLaunchTask": {
        "type" : "haxe",
	"args" : "active configuration"
      }
    },
    {
      "name": "HashLink (attach)",
      "request": "attach",
      "port": 6112,
      "type": "hl",
      "hxml": "compile.hxml",
      "cwd": "${workspaceRoot}",
      "preLaunchTask": {
        "type" : "haxe",
	"args" : "active configuration"
      }
    }
  ]
}```

Currently statics are only accessible through their full classpath.

They should be:

• listed as part of variables (statics) --- if we are in static function?
• evaluated from just their name inside the current class

See https://community.heaps.io/t/heaps-with-hashlink-debugger-issue/53

This seems to happen on dual GPU (Intel/Nvidia) Windows systems. When attempting to debug from vscode the program fails with an error like:

hldx / NVIDIA GeForce MX150: DXError 8007000E line 184 Called from h3d.impl.DirectXDriver.onDXError (h3d/impl/DirectXDriver.hx line 193)

Or other variants if forcing Intel GPU.

However, it's possible to start the debugger from the command line and attach to it. @ncannasse pointed me to the env supplied to node.spawn in HLAdapter.hx. Indeed omitting the empty env is sufficient to fix the issue. I'll provide a MR for a minimal env that works for me.

Stack overflows correctly trigger a break in debugger but no error message is displayed.

HashLink debugger version: 0.4.4
HashLink version: 1.7.0 and 1.8.0 (probably earlier as well, but these are the two I tried)
Haxe version: 4.0.0-preview.5
Heaps version: 1.4.0

I am not sure whether this is something that needs to be fixed in Heaps or the HashLink debugger. I have only had this issue when using the debugger in VS Code (and not when building from the command line), so I'm opening the issue here.

I have a Heaps project with a .gitkeep in my resource directory. This .gitkeep file wasn't completely empty and contained a UTF-16 BOM. When I tried to build or debug the HashLink target from VS Code I got the following non-useful error:

RangeError: Invalid code point 4186944

This would then take me to my launch.json file. A hex dump of my .gitkeep file looks like this:

FF FE 0D 00 0A 00

(Which strangely doesn't contain the code point mentioned in the error, unless I'm missing something.) I'm guessing this has to do with how Res.initEmbed embeds the resource. For the purpose of a minimal repro, my app looks like this:

class PongApp extends App
{
    public static function main()
    {
        Res.initEmbed();
    }
}

I haven't looked at the internals too much, but I'm guessing the possible fixes are:

• a) Make Heaps embed the resource in a different way so that arbitrary bytes won't break the debugger.
• b) Change the HashLink debugger to tolerate strange bytes that don't match the encoding scheme it expects (is the debugger looking at the source after macros have transformed it?)

In addition, I would really like error messages for cases where parsing/anything fails when processing an embedded resource. If the error had said something like Unexpected encoding for res/.gitkeep it would have made for a much better experience.

inline function such as Std.int() will add a "x" local variable to the context, whereas they should not.

VSCode stops debugging and brings up an "Overflow" error dialog with HashLink 1.7 x64 MSVC build. 32 bit works, compiled both from source in VS2017.

Simple hello world trips it, seems to be when sending last function in debugger.c handshake loop:

send(&m->code->nfunctions,4);
for(i=0;i<m->code->nfunctions;i++) {
   ...
   // VSCode debugger disconnects
   send(d->offsets,(d->large ? sizeof(int) : sizeof(unsigned short)) * (f->nops + 1));
}

class HelloWorld {
  static public function main():Void {
    trace("Hello World");
  }
}

Invalid eval path gives "Cannot read property xxx of undefined"
(eg hxd.fs.LocalFileSystem.WATCH_LIST)

The documentation (as shown in both github and the marketplace) do not state that the hashlink debugger works only with the x64 build of VSCode. Maybe just add a line saying that to the top of the README.md - if you run it in the 32 bit VSCode on Windows it simply fails to debug with an unspecified error.

Try to start simple heaps game and get this error:

Info:

OS: macOS Mojave 10.14.2 (18C54)
Code: 1.30.2 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8

Haxe Extensions

Name: Haxe Extension Pack
Id: vshaxe.haxe-extension-pack
Description: Everything you need for Haxe development
Version: 1.3.0
Publisher: vshaxe
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=vshaxe.haxe-extension-pack

Name: Haxe
Id: nadako.vshaxe
Description: Haxe language support
Version: 2.4.5
Publisher: nadako
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=nadako.vshaxe

Name: HashLink Debugger
Id: haxefoundation.haxe-hl
Description: Debugger for Haxe/HashLink applications
Version: 0.5.1
Publisher: Haxe Foundation
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=haxefoundation.haxe-hl

Name: HXCPP Debugger
Id: vshaxe.hxcpp-debugger
Description: Debugger for Haxe/HXCPP applications
Version: 1.1.1
Publisher: vshaxe
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=vshaxe.hxcpp-debugger

launch.json

{
            "name": "HashLink",
            "request": "launch",
            "type": "hl",
            "hxml": "compile_hl.hxml",
            "cwd": "${workspaceRoot}",
            "preLaunchTask": {
                "type": "hxml",
                "file": "compile_hl.hxml",
            }
}

Can't reproduce this error on Windows 10. Chrome Debugger work's fine.

Terminal start hashlink:

hl ./build/hl/game.hl 

A program field would be more consistent with other debuggers, and make cwd obsolete:

https://github.com/Gama11/HaxeRepro/blob/master/.vscode/launch.json

It would allow it to work with HXML files that have no -hl.

Moved from https://github.com/ncannasse/hashlink-debugger/issues/5

When creating conditional breakpoint, they act as a regular breakpoint and pause always instead of evaluating condition.

Haxe Compiler 4.0.0-preview.4+1e3e5e016
HL/JIT 1.7.0
HashLink Debugger 0.4.3
VSCode 1.27.2 x64
Windows 10 x64

As the title says, not sure if I'm doing anything wrong.

See the following video for reference:
https://i.imgur.com/l0bRHiP.mp4

I get a dynamic linking error from VS Code when trying to launch a debug session on any Haxe project:

I'm really not sure what is causing this. The final line of thks extension's JavaScript which is being referred to does in fact load a library; here's the Haxe before it's compiled:

I thought that an LD_LIBRARY_PATH or LD_PRELOAD could be messing with library loading, but according to VS Code's dev tools neither of these variables are defined in process.env.

I'm using Haxe 4.0.0-rc1, HashLink 1.9.0, extension version 0.6.0, VS Code 64-bit 1.32.3, and Ubuntu 18.04.

It seems showing the value for locals doesn't work ("Unknown identifier s")?

s exists in the output with -D dump=pretty, so it's not inlined by the analyzer or anything.

Moved from https://github.com/ncannasse/hashlink-debugger/issues/11

We should resolve package name according to Haxe rules.

HashLink debugger version: 0.5.1
HashLink version: 1.8.0
Haxe version: 4.0.0-preview.5+7eb789f54
Heaps version: 1.5.0

Clone of #29 that is reported fixed, potential regression?

I'm using the vscode plugin & the https://heaps.io/samples/world.html sample in a new project and upon using the vscode autogenerated HashLink (launch)/(attach) debug configs I get RangeError: Invalid code point 4038625

My auto-generated launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "HashLink (launch)",
            "request": "launch",
            "type": "hl",
            "hxml": "build.hxml",
            "cwd": "${workspaceRoot}",
            "preLaunchTask": "build"
        },
        {
            "name": "HashLink (attach)",
            "request": "attach",
            "port": 6112,
            "type": "hl",
            "hxml": "build.hxml",
            "cwd": "${workspaceRoot}",
            "preLaunchTask": "build"
        }
    ]
}

My tasks.json (I had to manually add the taskName field because preLaunchTask wasn't finding the task without it)

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "taskName": "build",
            "type": "haxe",
            "args": "active configuration",
            "problemMatcher": [
                "$haxe-absolute",
                "$haxe",
                "$haxe-error",
                "$haxe-trace"
            ],
            "group": {
                "kind": "build",
                "isDefault": true
            }
        }
    ]
}

A standard haxe build.hxml && hl world.hl works fine

Here's my directory structure:

Directory of D:\haxe\helloHL

12/09/2018  00:36    <DIR>          .
12/09/2018  00:36    <DIR>          ..
12/09/2018  00:16    <DIR>          .vscode
12/09/2018  00:02                48 build.hxml
12/08/2018  23:34    <DIR>          res
12/08/2018  23:59             1,468 World.hx
               2 File(s)          1,516 bytes

 Directory of D:\haxe\helloHL\.vscode

12/09/2018  00:16    <DIR>          .
12/09/2018  00:16    <DIR>          ..
12/09/2018  00:15               769 launch.json
12/09/2018  00:16               559 tasks.json
               2 File(s)          1,328 bytes

 Directory of D:\haxe\helloHL\res

12/08/2018  23:34    <DIR>          .
12/08/2018  23:34    <DIR>          ..
12/08/2018  23:33    <DIR>          .tmp
12/08/2018  23:32             7,956 rock.hmd
12/08/2018  23:34            38,233 rockTexture.jpg
12/08/2018  23:32            15,999 tree.hmd
12/08/2018  23:34            30,174 treeTexture.png
               4 File(s)         92,362 bytes

Failed to start hl process (Error: spawn hl ENOENT)

This should be replaced by a proper message saying that hl could not be found in path, etc.

This occurs when putting a breakpoint at the end of DirectXDriver.setRenderTarget()

When I have two different workspaces open in VSCode, and there's already an HL debug session running in one of them, starting one in the second gives me this error:

Dans la classe TradingPost, si je mets un break point sur le return final de la fonction, l'affichage de la variable v avec le debugger n'est pas bonne. Je t'ai mis un commentaire dans la fonction si besoin d'une repro.

A new error with the latest VSCode version. Run on windows:

Debug adapter process has terminated unexpectedly (Error: read error Error: read error at Socket.<anonymous> (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:387:585) at emitOne (events.js:121:20) at Socket.emit (events.js:211:7) at Pipe.Socket._destroy.cb._handle.close [as _onclose] (net.js:554:12))

Hi,i tried to compile to js and got fllowing error. Type not found : js.jquery.JQuery.
And i tried to compile with Haxe Compiler 3.4.7,just work fine.

Haxe Compiler 4.0.0-preview.5+7eb789f
HL/JIT 1.8.0
HashLink Debugger 0.4.4
VSCode 1.28.2 x64
macOS Mojave

/usr/local/lib/haxe/lib/heaps/1,4,0/h3d/mat/Material.hx:287: characters 14-30 : Type not found : js.jquery.JQuery
/usr/local/lib/haxe/lib/heaps/1,4,0/hxd/impl/AnyProps.hx:26: characters 14-30 : Type not found : js.jquery.JQuery

compile_js.hxml

-lib heaps
-js main.js
-main Main
-debug

I get this error on Ubuntu 18.04.
vscode 1.30
Haxe preview 5
Heaps & all git versions
Hashlink 1.8

Hashlink is compiled by my machine but I changed the location of hl to /usr/bin/ because I would get Failed to spawn hl ENOENT if hl was in /usr/local/bin.

When I run from terminal hl game.hl the window opens without issue.

When starting the debugger I get the aforementioned output in the Debug console.

Trying to follow getting started guide on heaps.io

.hl file is being compiled fine, but when I run debugger i get this error in extensions output:

/Users/n1kk/.vscode/extensions/haxefoundation.haxe-hl-0.4.4/node_modules/bindings/bindings.js:98
  if( lasterr ) throw lasterr;
                ^
Error: dlopen(/Users/n1kk/.vscode/extensions/haxefoundation.haxe-hl-0.4.4/node_modules/ref/build/Release/binding.node, 1): no suitable image found.  Did find:
	/Users/n1kk/.vscode/extensions/haxefoundation.haxe-hl-0.4.4/node_modules/ref/build/Release/binding.node: unknown file type, first eight bytes: 0x4D 0x5A 0x90 0x00 0x03 0x00 0x00 0x00
	/Users/n1kk/.vscode/extensions/haxefoundation.haxe-hl-0.4.4/node_modules/ref/build/Release/binding.node: unknown file type, first eight bytes: 0x4D 0x5A 0x90 0x00 0x03 0x00 0x00 0x00
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:166:20)
    at Object.Module._extensions..node (module.js:671:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:166:20)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:504:12)
    at Function.Module._load (module.js:496:3)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at bindings (/Users/n1kk/.vscode/extensions/haxefoundation.haxe-hl-0.4.4/node_modules/bindings/bindings.js:85:44)
    at Object.<anonymous> (/Users/n1kk/.vscode/extensions/haxefoundation.haxe-hl-0.4.4/node_modules/ref/lib/ref.js:5:47)

VSCode Version 1.28.2 (1.28.2), MacOS 10.14
node v10.12.0 (npm v6.4.1)

Tried reinstalling clean VSCode and just installed Haxe Extension Pack 1.3.0, didn't help.

Any ideas what is causing this?