3 ms·

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

by 0x0 9y ago

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 :)

eridius 9y ago
It shouldn't. Xcode usually switches to the shallowest stack frame that has source code available when hitting a breakpoint.
- 0x0 9y ago
  Oh, I was talking about uncaught exceptions where no breakpoint has been set.
  - eridius 9y ago
    Uncaught exceptions don't enter the debugger until it bubbles back up to main(), so the stack in the debugger is useless there.
    - 0x0 9y ago
      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.