I am running the latest version of chrome canary 91.0.4464.5 64bit MS Windows . The crashing is pretty random. You can set a breakpoint on a line and it might work and then you run some more and it crashes. Yes I get a DevTools disconneted error and the web page crashes..
On Wednesday, March 31, 2021 at 10:06:12 AM UTC-4 [email protected] wrote: > How does the DevTools crash look like? Do you get a "DevTools disconnected > from the page" error or anything on the terminal? What Chrome version are > you on currently? > > It would be great if you could share steps to reproduce, as so far I've > not managed to myself. > > Cheers, > Philip > > On Tue, Mar 30, 2021 at 8:48 PM Brian Gavin <[email protected]> wrote: > >> I also noticed adding -fno-inline to compiler options made things worse >> for setting breakpoints. >> >> On Tuesday, March 30, 2021 at 1:55:35 PM UTC-4 Brian Gavin wrote: >> >>> DevTool crashes. Unfortunately I do not have a simple example with >>> repro steps. >>> >>> Sorry, >>> Brian Gavin >>> >>> On Tuesday, March 30, 2021 at 9:32:32 AM UTC-4 [email protected] wrote: >>> >>>> Hi Brian, >>>> >>>> great to hear that things improved! >>>> I'd still like to get to the bottom of your remaining issues. What kind >>>> of crashes are you getting? Page/Renderer crashes or DevTools crashes? It >>>> would be great if you could share a reproducer, then I can debug what's >>>> going on! >>>> >>>> Cheers, >>>> Philip >>>> >>>> On Tuesday, March 30, 2021 at 3:25:06 PM UTC+2 Brian Gavin wrote: >>>> >>>>> Breakpoints are working much better with recent changes. Still >>>>> unable to see variable values in many cases and crashing, but nice >>>>> improvements. :) >>>>> >>>>> >>>>> On Monday, March 1, 2021 at 10:11:06 PM UTC-5 [email protected] >>>>> wrote: >>>>> >>>>>> I also encountered the same problem when I debug a qt5 app with dwarf >>>>>> in chrome devtools. I can see all the c++ source files in devtool, but >>>>>> some >>>>>> source code line can not set breakpoints and some line can set bp in the >>>>>> same file, which are all grayed out. >>>>>> 在2021年1月14日星期四 UTC+8 下午9:20:32<[email protected]> 写道： >>>>>> >>>>>>> Thanks for the infos! I tried to reproduce it with your pseudo code >>>>>>> but had no luck. I can see breakable lines in the MainLoopCB file. >>>>>>> Would >>>>>>> you mind filing a bug at crbug.com against >>>>>>> the Platform>DevTools>WebAssembly component? >>>>>>> >>>>>>> If possible, please include a minimal self-contained reproducer, >>>>>>> such as the two required sources and something like a makefile to >>>>>>> build. >>>>>>> You might also attach a binary if that's not too big! >>>>>>> >>>>>>> On Tuesday, January 12, 2021 at 8:03:37 PM UTC+1 Brian Gavin wrote: >>>>>>> >>>>>>>> yes, all of the line numbers are grayed out, but I can see all of >>>>>>>> my source files. I am using -g for linking and compiling -O0 only >>>>>>>> when >>>>>>>> linking. I can set breakpoints in my main() function and any code in >>>>>>>> other files called by the main() function. >>>>>>>> >>>>>>>> My code has a file main.cpp that holds int main() if I hack my >>>>>>>> code and a callback function for an event or my main loop callback I >>>>>>>> can >>>>>>>> set breakpoints for code in main.cpp but as soon as my code calls code >>>>>>>> outside of main.cpp. I can not set breakpoints in the code. >>>>>>>> >>>>>>>> pseudo code >>>>>>>> >>>>>>>> void MainLoopCB(void* data) >>>>>>>> { >>>>>>>> // If this function is not in main.cpp breakpoints will not >>>>>>>> work >>>>>>>> ClassInOtherFile(); >>>>>>>> } >>>>>>>> >>>>>>>> int main() >>>>>>>> { >>>>>>>> // Breakpoints work here and variables can be inspected >>>>>>>> int i=0; >>>>>>>> int sum=0; >>>>>>>> for(i=0;i<20;i++) >>>>>>>> { >>>>>>>> sum++; >>>>>>>> } >>>>>>>> emscripten_set_main_loop_arg(MainLoopCB,0,nullptr,true); >>>>>>>> >>>>>>>> return 0; >>>>>>>> } >>>>>>>> On Monday, January 11, 2021 at 9:57:38 AM UTC-5 [email protected] >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi Brian! >>>>>>>>> >>>>>>>>> By unable do you mean that all the line numbers in the sources >>>>>>>>> panel are grayed out? But you can see all source files? Are you using >>>>>>>>> those >>>>>>>>> flags both for compiling and linking? >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Philip >>>>>>>>> On Friday, January 8, 2021 at 4:22:05 PM UTC+1 Brian Gavin wrote: >>>>>>>>> >>>>>>>>>> Hello, >>>>>>>>>> I am excited to see the new ability to set breakpoints and view >>>>>>>>>> variables in Chrome. >>>>>>>>>> >>>>>>>>>> When I do a simple project with about 5 source files it works >>>>>>>>>> fairly well, but when I try to debug my large project with 100s of >>>>>>>>>> files. >>>>>>>>>> I am unable to set breakpoints in the callback functions such as >>>>>>>>>> mouse >>>>>>>>>> events and our callback function that draws to the screen at 60 fps( >>>>>>>>>> emscripten_set_main_loop_arg ). Is there a linker/compiler setting >>>>>>>>>> that >>>>>>>>>> helps this. I am using -g -O0 -fno-inline as flags for debugging. >>>>>>>>>> I am >>>>>>>>>> using emscripten SDK 2.0.11 with Chrome Canary. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/070198b1-d464-4dac-a323-af54964d67aan%40googlegroups.com >> >> <https://groups.google.com/d/msgid/emscripten-discuss/070198b1-d464-4dac-a323-af54964d67aan%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > > Philip Pfaffe > > Software Engineer > > [email protected] > > Google Germany GmbH > > Erika-Mann-Straße 33 > > 80636 München > > Geschäftsführer: Paul Manicle, Halimah DeLaine Prado > > Registergericht und -nummer: Hamburg, HRB 86891 > > Sitz der Gesellschaft: Hamburg > > Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten > haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, > löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, > dass die E-Mail an die falsche Person gesendet wurde. > > > > This e-mail is confidential. If you received this communication by > mistake, please don't forward it to anyone else, please erase all copies > and attachments, and please let me know that it has gone to the wrong > person. > > -- 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/54eb7a5c-464a-4678-aa55-d44fd9099612n%40googlegroups.com.
