Databases
StackOverflow2013
Postsdbo
POPreviously-Working Code Crashes Only in iOS5 as Static Library w/ EXC_BAD_ACCESS Code=1
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPreviously-Working Code Crashes Only in iOS5 as Static Library w/ EXC_BAD_ACCESS Code=1
    primarykey
    data
    text
    <p>So I have had a number of classes bundled together as a static framework using the universal framework project posted by Kyle here: <a href="https://github.com/kstenerud/iOS-Universal-Framework" rel="nofollow">https://github.com/kstenerud/iOS-Universal-Framework</a></p> <p>Things compile and run just fine on iOS 5.0 up through 6.0, and have for several months now - I generally just copy the resulting framework into my project, link it up, and use it. It uses ARC for most classes.</p> <p>Recently, I created a static library project from scratch in xcode 4.5 and copied all the classes from the framework into it. It compiled straight off, as did the project I added it to (previously used with the framework), but when I run it on my iPhone 4 w/ iOS 5.1.1, it crashes during runtime with an EXC_BAD_ACCESS message and doesn't highlight any specific code associated with the crash. Everything works well on the iOS 6.0 simulator, and an iPhone 4S I have that's running iOS 6.</p> <p>The most I've figured out is that the error is occurring within a (rather large) block that registers as a background process and uses a location manager. I'm currently back-installing the 5.1 simulator to see if that crashes too.</p> <p>Are there any major differences in the way static libraries and static frameworks are treated that I might not be aware of? Any significant differences between iOS 5 and 6 in that respect? I've played around with linker flags a little, including -ObjC and -all_load. Are there any pieces of code or error strings that would be helpful for me to post? I didn't include anything yet since i'm not entirely sure where the issue is...</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAmos
    1. USAmos
    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. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COhave u checked by enabling zombie.. it may show u whr ur code is getting crash..
      singulars
      1. POPreviously-Working Code Crashes Only in iOS5 as Static Library w/ EXC_BAD_ACCESS Code=1
      1. USvishy
    2. CORecompiled everything for the simulator, tried to run NSZombie detection on it, and everything worked! No EXC_BAD_ACCESS errors at all. Still happens on the device, though.
      singulars
      1. POPreviously-Working Code Crashes Only in iOS5 as Static Library w/ EXC_BAD_ACCESS Code=1
      1. USAmos
    3. COcheck out if u have any non ARC classes.. go through release/autorelease objects
      singulars
      1. POPreviously-Working Code Crashes Only in iOS5 as Static Library w/ EXC_BAD_ACCESS Code=1
      1. USvishy
 

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