[Interest] KDSOAP iOS 8 problems

Federico Buti bacarozzo at gmail.com
Mon Sep 29 18:55:57 CEST 2014


Hi all.

I'm developing a cross-platform app which comes in two forms: a "basic" one
and a "pro" one. The latter depending on the nice KDSoap library.

I've successfully re-compiled the library for Android/iOS and deployed the
apps to the app stores. So far, so good... until iOS 8!

Apart from known issues (e.g. screen rotation), I'm experiencing random
crashes at start-up but ONLY in the "pro" version. These crashes are not so
different from others reported on the Internet. Here is a log of the crash:


-----------------------------------------------
program received signal -111,
thread:b6e;qaddr:35a98ad0;00:00000000;01:cddac62f;02:90246516;03:01000000;04:01000000;05:808aa935;06:00004601;07:b4973b01;08:00000000;09:01000000;0a:cddac62f;0b:00726a33;0c:356fd632;0d:88973b01;0e:576fd632;0f:906fd632;10:30000080;metype:1;mecount:2;medata:1;medata:0;
program received signal -111,
thread:b6e;qaddr:35a98ad0;00:00000000;01:cddac62f;02:90246516;03:01000000;04:01000000;05:808aa935;06:00004601;07:b4973b01;08:00000000;09:01000000;0a:cddac62f;0b:00726a33;0c:356fd632;0d:88973b01;0e:576fd632;0f:906fd632;10:30000080;metype:1;mecount:2;medata:1;medata:0;
program received signal -111,
thread:b6e;qaddr:35a98ad0;00:00000000;01:cddac62f;02:90246516;03:01000000;04:01000000;05:808aa935;06:00004601;07:b4973b01;08:00000000;09:01000000;0a:cddac62f;0b:00726a33;0c:356fd632;0d:88973b01;0e:576fd632;0f:906fd632;10:30000080;metype:1;mecount:2;medata:1;medata:0;
program received signal -111,
thread:b6e;qaddr:35a98ad0;00:00000000;01:cddac62f;02:90246516;03:01000000;04:01000000;05:808aa935;06:00004601;07:b4973b01;08:00000000;09:01000000;0a:cddac62f;0b:00726a33;0c:356fd632;0d:88973b01;0e:576fd632;0f:906fd632;10:30000080;metype:1;mecount:2;medata:1;medata:0;
program received signal -111,
thread:b6e;qaddr:35a98ad0;00:00000000;01:cddac62f;02:90246516;03:01000000;04:01000000;05:808aa935;06:00004601;07:b4973b01;08:00000000;09:01000000;0a:cddac62f;0b:00726a33;0c:356fd632;0d:88973b01;0e:576fd632;0f:906fd632;10:30000080;metype:1;mecount:2;medata:1;medata:0;
program received signal -111,
thread:b6e;qaddr:35a98ad0;00:00000000;01:cddac62f;02:90246516;03:01000000;04:01000000;05:808aa935;06:00004601;07:b4973b01;08:00000000;09:01000000;0a:cddac62f;0b:00726a33;0c:356fd632;0d:88973b01;0e:576fd632;0f:906fd632;10:30000080;metype:1;mecount:2;medata:1;medata:0;
hit maximum number of consecutive signals, stopping
-----------------------------------------------


The wrong behaviour extends also to the previous version of the "pro" app,
delivered on July. Hence, I suppose it can be related to library loading
and changes made by Apple with the new OS. The "basic" version still works
perfectly without ANY crash at all.

Debugging execution with Xcode I obtain a EXC_BAD_ACCESS which should be
related to a wrong memory management.

My current devmachine setting is: Xcode 6.0.1 with Qt 5.3.2 on MacOsX 10.9.2

I've no clue on how to solve this issue. Any help would be really
appreciated. Thanks in advance!
F.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20140929/cba30f0e/attachment.html>


More information about the Interest mailing list