Open GoogleCodeExporter opened 8 years ago
I have the same SIGABRT crash on iOS 4.2 GM simulators.
No problem on decice, but it's hard to test without simulators.
Exact log >>
Detected an attempt to call a symbol in system libraries that is not present on
the iPhone:
strtod$UNIX2003 called from function dmstor in image Mapper.
If you are encountering this problem running a simulator binary within gdb,
make sure you 'set start-with-shell off' first.
Program received signal: “SIGABRT”.
(gdb)
Original comment by slatv...@gmail.com
on 12 Nov 2010 at 7:11
iOS 4.2/4.2.1 release and Xcode 3.2.5. The problem is still exists.
Original comment by slatv...@gmail.com
on 24 Nov 2010 at 10:15
Anyone ever get this figured out?
Original comment by kyle.han...@gmail.com
on 30 Nov 2010 at 10:46
I didn't have this problem, but I have somebody who also works on the same
project that ran into it. Here is what I did to fix it. I opened the
separate route-me project in the MapView folder. Then I updated the base-SDK
to 'Latest IOS (currently set to IOS 4.2)'. Then I sent him a copy of the
route-me project file (MapView.xcodeproj) and had him do a 'Clean all Targets'
for the route-me project. Then built the route-me project. Next I had him open
up my app project and had him do a 'touch' on the libMapView.a file. When he
ran the app again ,in the simulator, it worked.
Original comment by nepsu...@gmail.com
on 3 Dec 2010 at 6:11
I'd like to try this. Could u share the changed files?
Original comment by slatv...@gmail.com
on 3 Dec 2010 at 7:18
Check your base SDK - I found that I checked in a project file with the wrong
base SDK. I just changed my to Latest iOS
Original comment by marc...@gmail.com
on 29 Dec 2010 at 3:20
I am getting the same issue trying to run on simulator for 4.2. Never had this
on 4.0 or 3.2 simulator runs.
Original comment by bkgood...@gmail.com
on 21 Jan 2011 at 10:26
Setting the the base-SDK to Latest iOS (4.2) for both MapView.xcodeproj and
Proj4.xcodeproj fixed this issue for me.
Original comment by jt.stradling@gmail.com
on 6 Feb 2011 at 9:47
Original issue reported on code.google.com by
j.cimb.b...@gmail.com
on 28 Sep 2010 at 6:26