breakpoints

I'm looking to be able to have the debugger break when it reaches a particular string match. As an example, I might have something like this: Foo myObj = [self gimmeObj]; myObj might have a property called name . I want the debugger to stop on the assignment when [myObj.name isEqualToString:@"Bar"]; How can I set my conditional breakpoint in Xcode to do that? Peter N Lewis You can set a conditional break point in Xcode by setting the breakpoint normally, then control-click on it and select Edit Breakpoint (choose Run -> Show -> Breakpoints). In the breakpoint entry, there is a Condition column

I'd like to predefine some breakpoints in a gdb script and to invoke some special commands at these breakpoints and afterwards to automatically continue the program execution. So, ideally, I'd like to have a gdb script like the following: b someFunction ... if breakpoint from above reached do: print var1 call someOtherFunction continue done Additionally an unfortunate fact is, that I can't rely on the python interface for using breakpoints, as the gdb version at the server I currently work at is too old! You should take a look at the command command, which enables you to add gdb commands as a

I am using the Eclipse IDE. I don't know how effectively put breakpoints in Eclipse and go forward and backward into it. Can anyone help me? Can anyone suggest a site suitable for me? Googling gives many sites... Debugging with the Eclipse platform for one. James To put breakpoints in your code, double click in the left margin on the line you want execution to stop on . You may alternatively put your cursor in this line and then press Shift + Ctrl + B . To control execution use the Step Into , Step Over and Step Return buttons. They have the shortcuts F5 , F6 and F7 respectively. To allow

When working with breakpoints in Eclipse I sometimes notice that they have different icons / annotations (markers on left sidebar). Sometimes it's just a blue ball, sometimes it has a checkmark on it and sometimes it is crossed. What do all these annotations mean? blue ball: regular breakpoint, active (possibly with a hit count set) empty ball (i.e. white): breakpoint has been disabled (remove checkmark in the breakpoint view, or disable in context menu) diagonal line through breakpoint: all breakpoints have been disabled (button skip all breakpoints in breakpoint view) question mark next to

Is it possible to set the breakpoint in Xcode to have the debugger stop only on unrecognized selector? I have other exceptions that are triggering, and I only want to trigger on the unrecognized selector exception, nothing else. Setting a symbolic breakpoint for -[NSObject doesNotRecognizeSelector:] should do the trick. In Xcode 4, press cmd + 6 to go to the Breakpoint Navigator, then click the + and choose "Add Symbolic Breakpoint…". Configure. 来源： https://stackoverflow.com/questions/7156090/creating-breakpoint-in-xcode-for-unrecognized-selector

I'm getting a NullPointerException in a Class from a 3rd party library. Now I'd like to debug the whole thing and I would need to know from which object the class is held. But it seems to me that I cannot set a breakpoint in a Class from a 3rd party. Does anyone know a way out of my trouble? Of course I'm using Eclipse as my IDE. Update: the library is open-source. The most sure-fire way to do this (and end up with something that's actually useful) is to download the source (you say that it is open-source), and set up another "Java Project" pointing at that source. To do that, get the source

Visual Studio remembers breakpoints from previous debugging sessions, which is awesome. However, when I'm debugging, and I clear one of these "old" breakpoints by clicking on it, it's only temporarily deleted. What I mean is the next time I debug, the breakpoint that I thought I removed is back. This is super annoying--is there a setting to make it not do this? go to Debug menu then Delete All Breakpoints Ctrl+Shift+F9 The problem is that child breakpoints of your breakpoints persist. Child breakpoints are created (in certain situations) when setting breakpoints during a debug session. A