login about faq


I have a number of crash reports that indicate that my iOS app has crashed with a SIGTRAP inside places like ckSevereError, XString::clear, LogBase::LogDataLong, Pkcs1::v1_5_decode, Pkcs7_EnvelopedData::loadXml, Pkcs7::loadPkcs7Der, Rsa2::decryptAndUnpad, DataBuffer::loadFileUtf8, ClsCrypt2::decryptData, LogEntry2::allowMoreSubEntries.

I'm assuming that a C++ exception is raised in those locations? It's idiomatic for Objective-C APIs not to raise any exceptions except for the case of programmer error (eg. missing arguments etc) and so the Chilkat API should trap any C++ exceptions and return an error in those cases (in the case of the Chilkat APIs I guess that would be placing the error string in lastErrorText since none have NSError outvar parameters).

Is that what is supposed to be happening? If not, I suggest that it should, but for now should I be wrapping all my Chilkat API calls with try/catch? And if so, can I ever do anything useful with the exception body?


asked Aug 19 '14 at 08:35

gumby's gravatar image


Download and test using the latest version (v9.5.0.43)

If you already have the latest version, try this one:

If the problem still exists, please report back.


answered Aug 19 '14 at 08:49

chilkat's gravatar image

chilkat ♦♦

I'm actually working on a release that includes 9.5.0 (previously a pre: 9.5.0 version was used).

Are you suggesting that because some specific crashes are fixed, or because you now catch C++ exceptions in the Cocoa API and you didn't use to? If the former but not the latter, then I will still need to catch potential C++ exceptions myself.

(Aug 20 '14 at 02:40) gumby

Worth pointing out that these are not crashes that I can replicate, but I have 30 crash reports or so (for a very small user base), so it's not some very rare random race condition.

(Aug 20 '14 at 02:47) gumby

Note that this may be related to a threading race condition in my code as per #6251, I'll report back after further testing.

(Aug 20 '14 at 05:52) gumby
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Aug 19 '14 at 08:35

Seen: 2,360 times

Last updated: Aug 20 '14 at 05:52

powered by OSQA