Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you want to stop your program at the point where it crashes, you need to add an Exception breakpoint.</p> <p>Go to the Breakpoint Navigator, click on the plus button, and select Add Exception Breakpoint...</p> <p><img src="https://i.stack.imgur.com/gP4iq.png" alt="enter image description here"></p> <p>In XCode 5 it will add it straight away, but in previous versions you will need to select : All exceptions </p> <p>This will stop at where you NSArray is being accessed out of bounds, and then you can debug.</p> <p><strong><h1>Edit:</h1></strong></p> <p>After your program stops, you should be able to see in XCode the line where it crashes. If you don't see the line in XCode, you can in the debugger type:</p> <p>(lldb) bt</p> <p>'bt' will print all the steps that the program did to get there, and it will give you the information about what methods were called.</p> <p>If that doesn't give you the info you need, you can try this way:</p> <p>Your second option is to repeat the steps before, but instead of selecting Add Exception Breakpoint... you should choose Ad Symbolic Breakpoint...</p> <p>Once you select it, a pop up window will prompt to enter some values. Enter the following:</p> <p><img src="https://i.stack.imgur.com/OVyX1.png" alt="enter image description here"></p> <p>Before crashing it should stop. At that point you can navigate to the Debug Navigator to see what the steps were, and spot the location out:</p> <p><img src="https://i.stack.imgur.com/5oZiD.png" alt="enter image description here"></p> <p>As you can see setPrivateProperty is the last time a method was called before stopping.</p> <p>If the Debug Navigator doesn't give you any information, you can always go to the debugger and type:</p> <p>(lldb) bt</p> <p>As before, 'bt' will trace back all the steps to get there in more detail.</p> <p>All this info should be enough to debug your program. If you need help to interprete the 'bt' output, that's another thread!</p>
    singulars
    1. This table or related slice is empty.
    1. POApp crashing: Index out of bound at random places
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USuser1447414
    1. USuser1447414
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhen the breakpoint is hit you may have to "continue" a couple of times to get the message since you are in the exception handler prior to it logging the error information.
      singulars
      1. PO
      1. USzaph
    2. COYeah I added the break point with the options all and objective C but when the crash happens it just logs All Objective C exception and not the place where it is happening. And the next line is index out of bound. This is troubling me for some time now and is just frustrating. :(
      singulars
      1. PO
      1. USAtif Imran
    3. CO@Zaph If the breakpoint can stop at the exact point where the array emptied or index is out of bounds that can really help, but the thing is it is just printing "All Objective-C Exception" which is not at all helpful or may be I am missing something?
      singulars
      1. PO
      1. USAtif Imran
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload