The best debugging workflow is still to create a native build of your code and debug that in a "traditional" debugger.
It's far from perfect, but since most source code should be platform-agnostic, and assuming that bugs are evenly distributed, it works pretty well in most real-world debugging situations. For emscripten-specific code, fall back to "printf-debugging". Making this whole process of working with native and cross-compiled build targets easier was one important reason why I created fips: http://floooh.github.io/fips/ Cheers, -Floh. On Thursday, 4 July 2019 00:50:41 UTC+2, adam crockett wrote: > > To clarify this is regarding emscripten and not generally c++ -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/8a65f01a-544b-4d4f-af6a-2c69ad4f853b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
