breakpoints

When I add a breakpoint to some C# code during run-time, it gets hit. How does this actually happen? I want to say that when running in debug mode, Visual Studio has references for code blocks, and when a breakpoint is added during run-time, it would be activated once that reference is called in the compiled code. Is that a correct assumption? If so, can you please provide more details about how that works? This is actually a rather large and complicated topic, and it is also architecture-specific, so I'll only aim in this answer to provide a summary of the common approaches on the Intel (and

I just upgraded to the App Engine 1.7.6 SDK for my python app and realised that breakpoints no longer work in PyDev (Eclipse plugin) when using the new dev_appserver.py . Does anyone know of a way of enabling them again? I assume the new server is spawning a new process for the web server, and the debugger isn't attaching to that one. I'm not sure how to configure it to do that though. In the meantime I am using the old_dev_appserver.py server. Michael Kariv UPDATE 2012-07-27: Following the comment, I verified, the issue is solved after updating to PyDev. 2.8 and App Engine 1.8.2 OBSOLETE: I

When debugging, changes to breakpoints are only persisted for that debugging session. Once the debugger detaches the breakpoints are restored to their 'pre-debug' state. I can appreciate this is sometimes useful, and understand why it defaults this way. However - does anyone know if there is an option to disable this functionality (in VS2010) such that if I delete/disable/add a breakpoint during debugging the changes will persist the next time I start debugging? You can remove the breakpoint whilst debugging by using the Breakpoint Management Window (Debug -> Windows -> Breakpoints). From

In Eclipse, I would like to set a breakpoint on a Java default constructor . I can't simply double click to the left of any line of code since default constructors have no source code - they are implicitly generated by the Java compiler. I'd like to be able to set such a breakpoint without modifying the existing code . user655063 If the code where you want to set a breakpoint in, is on the build path and not in your project itself, then if you open the Outline view, you'll see that the default constructor is present there, and you can right-click on it and choose Toggle Method Breakpoint .

I am trying to set a breakpoint in linux in gdb for a program creating threads. I would like to set a breakpoint on thread creation, but unfortunately pthread_create is a versioned symbol, and I can't get its full name. If I type: catch thread_start I get Catch of thread_start not yet implemented How is the best way to catch thread creation in gdb for this situation? Try this: (gdb) b __pthread_create_2_1 Or build your own GDB with this patch applied. Or try the latest pre-release GDB here , which should allow you to do "catch syscall clone" OK, so in case I didn't really understand you, or my

Is there a way to tell the debugger to stop just before returning, on whichever statement exits from the method, be it return, exception, or fall out the bottom? I am inspired by the fact that the Java editor shows me all the places that my method can exit - it highlights them when you click on the return type of the method declaration, (Mark Occurrences enabled). [eclipse 3.4] Put a breakpoint on the line of the method signature. That is where you write public void myMethod() { Then right-click on the breakpoint and select "Breakpoint Properties". At the bottom of the pop-up there are two

Is there a command line argument or an environment variable that disables the "break on first line" feature of the node debugger? There are actually two debugger concepts in node: V8 debugger (with its TCP-based protocol) and a node command-line debugger (CLI). When you run node debug app.js , a debugger CLI is run in the master node process and a new child node process is spawned for the debugged script ( node --debug-brk app.js ). The option --debug or --debug-brk is used to turn on V8 debugger in the child process. The difference between --debug and --debug-brk is that the latter one adds a