Yeah, debugging is definitely one of the bigger missing pieces here. This will hopefully improve soon in toolchains and browsers, there is ongoing work on it. Meanwhile debugging a parallel native build is often best, as mentioned.
On Thu, Apr 4, 2019 at 8:56 PM Александр Гурьянов <[email protected]> wrote: > Agree, I never debug emscripten output. Source map never works for big > code bases. So all bug fixing done by playing with C++ native build, > in hope that it will be ported 1:1, actually it's almost true. > > пт, 5 апр. 2019 г. в 03:28, Brian Gavin <[email protected]>: > > > > My experience with source maps is similar to Floh. Kind of works for > very simple hello world apps but even then there are some lines I can not > set breakpoints. No variable inspection. Stepping into and out of > functions does not always work. > > > > Unfortunately my debugging technique is lots of prints and dump > callstack. You need to plan for development time to take longer then a > regular C++ application. > > > > Better debugging is my number 1 feature wish. > > > > Brian Gavin > > > > -- > > 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]. > > For more options, visit https://groups.google.com/d/optout. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
