Clever Geek Handbook

How do I tell the Xcode debugger to stop only at breakpoints? (not with exceptions)

I am writing a third party plugin for a closed source application. I have a problem with the Xcode debugger.

I would like to use a debugger to execute the plugin code that I am writing. To do this, I set a breakpoint in my code, I started the host application, and then connected the Xcode debugger to the host application process. My problem is that instead of stopping at my breakpoint, the debugger stops instead of an exception thrown by another part of the program. (In particular, it: Thread 2: EXC_ARITHMETIC (code=EXC_i386_DIV, subcode=0x0)

)

This exception is thrown so often that it actually prevents the execution of the code I'm really interested in.

I cannot catch and handle this exception because I do not have source code for the part of the application that is throwing it.

In this situation, can anyone suggest how I can debug my code? Is there a way to tell the Xcode debugger to just "ignore" this particular exception EXC_ARITHMETIC

and instead only stop at the breakpoints I've explicitly set?

UPDATE

@ user1118321 suggested disabling exception breakpoints using the breakpoints bar. I tried to do this using the settings shown here.

enter image description here

I thought that selecting "Auto continue after evaluation" might cause the debugger to stop. This is not true.

I also tried sending cont

to the debugger after stopping. This doesn't work either.

enter image description here

Can you advise me what settings should I put in here to stop the debugger on my exception EXC_ARITHMETIC

?

+3


source to share


2 answers


I followed the links suggested by @ user1118321. After hours of head scratching, I couldn't figure out how to disable or handle integer division by null exception. If anyone has any ideas I would love to hear them.

However, I found a workaround which is to use GDB instead of XCode. Unlike XCode, GDB doesn't seem to stop at EXC_ARITHMETIC

and allows me to step into my code. So for now I'm going to switch to GDB for debugging.



EDIT

The second (best) workaround, in my case, involved suspending the thread that was throwing the exception. This also allowed me to execute my plugin code.

0


source


This is an integer division by zero error exception. As far as I know, they are not propagated as C ++ exceptions, so you cannot break them.



Does this happen even if your plugin is not loaded? If it isn't, your plugin is calling division by zero somehow.

+3


source






More articles:


All Articles