update 4.0.0 StackBlitz example update RC.1 Plunker example In the browser console on the top-left (filter symbol) select plunkerPreviewTarget (or launch the demo app in its own window) then enter for example Select a component in the DOM node and execute in the console ng.probe($0); or for IE – thanks to Kris Hollenbeck (see comments) … Read more
Yes – it’s known as printf() debugging, named after the ubiquitous C function: Used to describe debugging work done by inserting commands that output more or less carefully chosen status information at key points in the program flow, observing that information and deducing what’s wrong based on that information. — printf() debugging@everything2 Native users of … Read more
yupp, I’ve successfully used node-inspector. If you want permanent breakpoints, simply insert debugger; in your code. See http://nodejs.org/api/debugger.html. Making node wait until a debugger is attached, using node –inspect-brk script.js (previously node –debug-brk script.js), can also be very helpful.
Is there a gdb command to finish a loop construct? Execute until on the last line of the loop, or until NNN where NNN is the last line of the loop. (gdb) help until Execute until the program reaches a source line greater than the current or a specified location (same args as break command) … Read more
Run cscript.exe for full command args, I think cscript //X scriptfile.vbs MyArg1 MyArg2 will run the script in a debugger.
I was able to debug gradle sources (including plugins) using -Dorg.gradle.debug=true (found on gradle forum): Stop daemons if any: ./gradlew –stop Run ./gradlew <task> –no-daemon -Dorg.gradle.debug=true Connect remotely to gradle process (port 5005) – if using IntelliJ IDEA, see OP’s image above It should stop on breakpoints now. BTW, I have created a separate IntelliJ … Read more
Bare minimum -Og/-O0 -O0 basically tells the compiler to make no optimisations. Optimiser can remove some local variables, merge some code blocks, etc. and as an outcome it can make debugging unpredictable. The price for -O0 option is very slow code execution, but starting from version 4.8 GCC compilers (including the Fortran one) accept a … Read more
Step in: means that if there is a function call, it goes inside the function and you can see how the function is executing line by line till it returns and you go back to the next line right after the function call. Step over: means that if there is a function call, it just … Read more
It might be a bug. Please file a Connect bug with a repro if you have one. In the meantime, you might be able to workaround the problem by setting the debugger options to use the legacy debug engine: Tools -> Options -> Debugging -> General: check both “Use the legacy C# and VB expression … Read more
A good bit of time has passed since I originally posted this question. I’ll answer it myself in case my mistake can assist anyone. I never got a “solution” to the original problem. At a much later date I switched across to the npm release of the sdk and it worked. But before that time … Read more