Is there any easier way to trace down code, even without checked variables content, just to see the callstack?
On Wednesday, October 21, 2015 at 3:58:55 PM UTC-4, Alon Zakai wrote: > > In my experience very large projects are indeed hard to get running in > browser debuggers. They just haven't been optimized for that size code yet, > I think. > > I do most of my debugging using dump(), which writes to stdout in the > console firefox was started from. (You need to set > browser.dom.window.dump.enabled in about:config for that to work.) Or > alert() when I want things to be paused. Or just console.log() when the > amount of output is small. > > On Wed, Oct 21, 2015 at 11:02 AM, Robert Goulet <[email protected] > <javascript:>> wrote: > >> Hi all, >> >> I'm trying to setup debugging in-browser, but it doesn't work for me, and >> I am wondering if it's just related to the size of my project? Does anyone >> successfully used breakpoints in code built with -g4 in Firefox Nightly? >> Everytime I add a breakpoint, it just freeze Firefox and I have to kill it. >> Please share your experience and tips. Thanks! >> >> -- >> 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] <javascript:>. >> 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.
