3 ms·
asm.js is just JavaScript, it isn't a new VM with exposed low-level binary details. You wouldn't need to use DWARF or write your own low-level debugger integrat
by azakai 14y ago
asm.js is just JavaScript, it isn't a new VM with exposed low-level binary details. You wouldn't need to use DWARF or write your own low-level debugger integration. You can debug code on it of course, the right approach would be to use the JS debuggers that all web browsers now have, with SourceMaps support.
The goal with asm.js is to get the same level of performance as native code, or very close to it. But it isn't a new VM like PNaCl, it runs in an existing JS VM like all JavaScript does. That means it can use existing JS debugging, profiling, etc.
- pifflesnort 14y ago> You can debug code on it of course, the right approach would be to use the JS debuggers that all web browsers now have, with SourceMaps support. That's not really a replacement for a real language and architecture-(VM or otherwise)-aware debugger. > That means it can use existing JS debugging, profiling, etc. Which is a problem, because all of that stuff is awful compared to the state of the art of modern desktop and mobile tooling.
- azakai 14y agoMatter of opinion, I actually prefer to debug C-compiled-to-JS than C-compiled-to-native these days. Mainly because I can script debugging procedures directly in the JS source and just run them. But sure, if you prefer gdb or such, then the web platform is not going to be a perfect match for you.