Databases
StackOverflow2013
Postsdbo
POiOS: How to get stack trace of an unhandled std::exception?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POiOS: How to get stack trace of an unhandled std::exception?
    primarykey
    data
    text
    <p>If an unhandled NSException is thrown, the stack trace has a section like this:</p> <pre><code>Last Exception Backtrace: 0 CoreFoundation 0x32bd688f __exceptionPreprocess + 163 1 libobjc.A.dylib 0x34b7b259 objc_exception_throw + 33 2 CoreFoundation 0x32bd65c5 -[NSException init] + 1 3 Foundation 0x37296bd7 -[NSObject(NSKeyValueCoding) valueForUndefinedKey:] + 263 ... </code></pre> <p>But if std::exception is thrown, i get only this:</p> <pre><code>Thread 0 Crashed: 0 libsystem_kernel.dylib 0x34f2632c __pthread_kill + 8 1 libsystem_c.dylib 0x31e4c208 pthread_kill + 48 2 libsystem_c.dylib 0x31e45298 abort + 88 3 libc++abi.dylib 0x33bcaf64 abort_message + 40 4 libc++abi.dylib 0x33bc8346 default_terminate() + 18 5 libobjc.A.dylib 0x349f4368 _objc_terminate + 164 6 libc++abi.dylib 0x33bc83be safe_handler_caller(void (*)()) + 70 7 libc++abi.dylib 0x33bc844a std::terminate() + 14 8 libc++abi.dylib 0x33bc981e __cxa_rethrow + 82 9 libobjc.A.dylib 0x349f42a2 objc_exception_rethrow + 6 10 CoreFoundation 0x329a5506 CFRunLoopRunSpecific + 398 11 CoreFoundation 0x329a5366 CFRunLoopRunInMode + 98 12 GraphicsServices 0x32af2432 GSEventRunModal + 130 13 UIKit 0x34f84cce UIApplicationMain + 1074 14 APP_NAME 0x00086b10 main (main.m:68) 15 APP_NAME 0x00071b98 start + 32 </code></pre> <p>How do I get the exact crash info from this crash log? </p> <p>Update --</p> <p>I've given HockeyApp a shot, but it has the same limitation as iTunes crash logs - it doesn't tell me the stack for an unhandled C++ exception. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMar0ux
    1. USMar0ux
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POiOS: How to get stack trace of an unhandled std::exception?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POiOS: How to get stack trace of an unhandled std::exception?
      1. USroger
      1. VTFavorite
    3. VO
      singulars
      1. POiOS: How to get stack trace of an unhandled std::exception?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you using a third party tool like crittercism, or testflightapp to get the reported crashes. You have to upload a dsym file and then it will symbolicate the crashes and it will show you the exact line where the crash occurred. To find the dsym file, you can right click the .ipa file in the organizer window or where ever you stored it and right click and show Contents.
      singulars
      1. POiOS: How to get stack trace of an unhandled std::exception?
      1. USSrikanth
    2. COI'm not using any third party tool. Can you recommend one? Also, I suspect these tools might not handle C++ exceptions - do you know of anyone that does?
      singulars
      1. POiOS: How to get stack trace of an unhandled std::exception?
      1. USMar0ux
    3. CONot sure about that. But here you go, there is another question similar to yours: http://stackoverflow.com/questions/11883069/how-to-decode-a-dsym-file-crash-log
      singulars
      1. POiOS: How to get stack trace of an unhandled std::exception?
      1. USSrikanth
 

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