If you are still in lldb when you see this log, you should be able to just do:
(lldb) image lookup -va <SYMBOL_ADDRESS> for all the addresses in the third column to see the correct symbols. Jim > On Aug 25, 2016, at 12:15 PM, Carl Hoefs <newsli...@autonomy.caltech.edu> > wrote: > > >> On Aug 25, 2016, at 12:04 PM, Jens Alfke <j...@mooseyard.com> wrote: >> >> >>> On Aug 25, 2016, at 11:53 AM, Carl Hoefs <newsli...@autonomy.caltech.edu> >>> wrote: >>> >>> I figured out that the following is Xcode's humorous way of saying "only >>> change the UI from the main thread". Okay, got it. But what's with all the >>> <redacted> stuff in the call traceback? It make it essentially useless. >> >> Where did you get the backtrace from? Usually when there are no real symbol >> names, it means the app has had debug symbols stripped out and there’s no >> dSYM file available to provide symbol names. >> > This occurred while running my iOS app from Xcode, connected to my iPhone. In > Xcode I have the "All Exceptions" breakpoint disabled (otherwise it would > break in some thread for "apparently no reason"). Xcode generates this > backtrace in the bottom console log output area. > > How does one build to explicitly include debug symbolication info? > -Carl > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Xcode-users mailing list (Xcode-users@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/xcode-users/jingham%40apple.com > > This email sent to jing...@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
