<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Debug on Michal Zygar</title>
    <link>https://www.mzygar.com/tags/debug/</link>
    <description>Recent content in Debug on Michal Zygar</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>All rights reserved - 2019</copyright>
    <lastBuildDate>Mon, 24 Jun 2019 21:23:00 +0200</lastBuildDate>
    
	<atom:link href="https://www.mzygar.com/tags/debug/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Debugging app terminating with uncaught exception of type NSException</title>
      <link>https://www.mzygar.com/post/debug-swift-uncaught-exceptions/</link>
      <pubDate>Mon, 24 Jun 2019 21:23:00 +0200</pubDate>
      
      <guid>https://www.mzygar.com/post/debug-swift-uncaught-exceptions/</guid>
      <description>Every now and then when working on the new features, our app crashes. Easy, peasy, right? Happens all the time. However sometimes all you can see is:
libc++abi.dylib: terminating with uncaught exception of type NSException  and then you wonder: Where did the stack trace go? The error message is not really helpful and asking lldb for more info using expr $arg1 does not work. It may cause you to be stuck for a couple of hours, trying to pinpoint the cause of the exception.</description>
    </item>
    
  </channel>
</rss>