NodeJS creates a v8debug global object when running in debug mode: node debug script.js So, a possible solution would be: var debug = typeof v8debug === ‘object’; For my use case, I use it because I want to avoid passing environment variables. My main node process starts child node processes and I want a node … Read more
Everytime docker successfully executes a RUN command from a Dockerfile, a new layer in the image filesystem is committed. Conveniently you can use those layers ids as images to start a new container. Take the following Dockerfile: FROM busybox RUN echo ‘foo’ > /tmp/foo.txt RUN echo ‘bar’ >> /tmp/foo.txt and build it: $ docker build … 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
There’s the more general but perhaps not as helpful to you Wireshark. One of the SO server sites might be better suited for your question. In fact, it’s already been asked on SuperUser.
To break on all exceptions, caught or uncaught: Open the Breakpoints window via Run -> View Breakpoints. The Breakpoints dialog appears. In the left pane, scroll to the bottom. Select Any exception under Java Exception Breakpoints With Any exception selected, on the right pane, configure as follows: Suspend: checked All: selected Condition: !(this instanceof java.lang.ClassNotFoundException) … Read more
I imagine there are better ways to do it, but the finish command executes until the current stack frame is popped off and prints the return value — given the program int fun() { return 42; } int main( int argc, char *v[] ) { fun(); return 0; } You can debug it as such … Read more
Yes! With the new version 7.0 gdb, you can do exactly that! The command would be “reverse-step“, or “reverse-next“. You can get gdb-7.0 from ftp.gnu.org:/pub/gnu/gdb If you run into the error: Target child does not support this command. then try adding target record at the beginning of execution, after starting run. Edit: Since GDB 7.6 … Read more
This won’t give you the line number, but it will tell you where the failure happens in the call stack which is very helpful: traceback() [Edit:] When running a script from the command line you will have to skip one or two calls, see traceback() for interactive and non-interactive R sessions I’m not aware of … Read more
UPDATE: As written in this answer, Stackdriver Logging is the preferred method of logging now. Use console.log() to log to Stackdriver. Logger.log will either send you an email (eventually) of errors that have happened in your scripts, or, if you are running things from the Script Editor, you can view the log from the last … Read more
What I’d like to do is insert a bit of code at the particular point that I want to start debugging. I usually do it like this: volatile int done = 0; while (!done) sleep(1); Attach GDB (you’ll be inside sleep). Do finish, then set var done = 1, and enjoy the rest of your … Read more