News for hackers. Stuff that matters.

A comment on Xcode 9.1 Improves Display of Fatal Errors. Parent comment

Re:Xcode 9.1 Improves Display of Fatal Errors by 0x0 on Friday October 06, 2017 @03:20PM (#15419610)
Thanks for the tip. It's usually not a problem to figure out what's wrong (the exception is dumped to the debugger), but it's a bit useless that the main editor in xcode switches to an irrelevant disassembly view at the same time :)
[ Parent | on HN ]
Re:Xcode 9.1 Improves Display of Fatal Errors by eridius on Friday October 06, 2017 @03:31PM (#15419703)
It shouldn't. Xcode usually switches to the shallowest stack frame that has source code available when hitting a breakpoint.
[ Parent | on HN ]
Re:Xcode 9.1 Improves Display of Fatal Errors by 0x0 on Friday October 06, 2017 @03:50PM (#15419844)
Oh, I was talking about uncaught exceptions where no breakpoint has been set.
[ Parent | on HN ]
Re:Xcode 9.1 Improves Display of Fatal Errors by eridius on Friday October 06, 2017 @04:27PM (#15420158)
Uncaught exceptions don't enter the debugger until it bubbles back up to main(), so the stack in the debugger is useless there.
[ Parent | on HN ]
Re:Xcode 9.1 Improves Display of Fatal Errors by 0x0 on Friday October 06, 2017 @05:32PM (#15420636)
Right, I was hoping this new Xcode 9.1 feature could improve upon that for Objective-C as well. Perhaps capturing a copy of the stack when the exception is raised, so it open the main editor window on the appropriate source line where that exception was raised.
[ Parent | on HN ]