Closed sourav-dey closed 5 months ago
ummm....
sorry but you did not Enter steps to reproduce
:flushed:
by just judging the stack trace
this is triggered by tree view > file name > right click > make run
but i cannot reproduce this error
can you provide the steps / screenshot of what you click such that this error occur?
Hey, It was due to the gdb-debugger package that I installed. Apparently, after installing that package -> adding breakpoints -> then running make-run caused that problem. There might be some weird mismatch happening between the two packages. I deleted gdb-debugger and it works great.
You can go ahead and close the issue, or if you are interested in whats the dependancy that caused this, I can reinstall gdb-debugger and get a more detailed answer.
Thanks & Regards, Sourav
On Mar 24, 2017, at 6:13 PM, Tom Lau notifications@github.com wrote:
ummm.... sorry but you did not Enter steps to reproduce 😳
by just judging the stack trace this is triggered by tree view > file name > right click > make run but i cannot reproduce this error can you provide the steps / screenshot of what you click such that this error occur?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
[Enter steps to reproduce:]
Atom: 1.15.0 x64 Electron: 1.3.13 OS: Microsoft Windows 7 Enterprise Thrown From: gcc-make-run package 0.2.9
Stack Trace
Uncaught TypeError: Path must be a string. Received null
Commands
Non-Core Packages