As part of my company's (Tableau Software) work with Emscripten, we've wanted to come up with better tooling around debugging. 3 main pain points we're hoping to address:
1. Debugging large code bases results in large (50+MB) size output Javascript, which prevents any sort of interactive debugging, at least on the tools I've used 2. Heap allocated data is pretty opaque 3. Source maps are currently busted on any level of optimization I have a work in progress design doc here: https://gist.github.com/hackcasual/ea77cc31c6dafdda7274 Changes to JSBackend to output the file format and add in the debug intrinsics are here: https://github.com/kripken/emscripten-fastcomp/compare/incoming...hackcasual:tableau-debugger-work I've got an initial driver (though out of sync with the format generated in the current changes to JSBackend), you can see here to have some understanding of how the types are interpreted: https://gist.github.com/hackcasual/efb93d70c4c3e87cd1ee More work needs to be done to get this into shipping shape, but I'd like to kick of discussions now. Thanks! Charles Vaughn -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
