Is Xcode debugging/crash report in Swift broken?

I've been working with Swift for over a year now and things seems to be only getting worse with each new Xcode release.

Is it only here that crashes in a app aren't reported correctly? Most of the time it's only SIGBRT or EXC_BAD_INSTRUCTION on main() (yes I use a main.m in my project):

That's not helpful. If I don't add an 'All Exceptions' breakpoint, I can't find where the crash happened. I just got used with not having any help at all from LLVM about any errors on my Swift code, and even then:

Is there something I'm missing here? I feel like back when I was programming with Objective-C things were much better.

UPDATE

I found this solution: https://stackoverflow.com/a/27356008/447360

Which helps sometimes:

Still looking on how to get the exception/error message to show up (again) in Xcode.

Answers


Ok, so I finally was able to improve the debugging info for breakpoints.

Basically you should create a "All Exceptions" breakpoint like this:

This is for Xcode 7+ only.

Credit:

http://natashatherobot.com/xcode-debugging-trick/

https://stackoverflow.com/a/31471663/447360

https://stackoverflow.com/a/4535007/447360


Check if the "Debug -> Debug Workflow -> Always Show Disassembly" is turned off.


Need Your Help

Local Human task service jBPM

java workflow jbpm

I am using jBPM 5.3.0, but i have a problem when i try to implement LocalTaskService for Human Task.

Alternating Columns of 2 SQL Queries

c# sql asp.net oracle

I have an oracle query that gets data from two different tables, displaying them as: