Error Resetting Objc Debugger Mode

the error message instruct? And of course I don't know how to fix the error. I'm trying to read a very nslog swift large array into and out of memory while the program is

Cocoalumberjack

running, save it to memory when the program shuts down and read it back when the program restarts.

Thread 1 Signal Sigabrt

Thanks for any help you can give me.killquitThe Debugger has exited with status 0.[Session started at 2010-02-02 21:32:53 -0800.]GNU gdb 6.3.50-20050815 (Apple version gdb-1346) (Fri Sep 18 20:40:51 UTC 2009)Copyright

Swift Logging

2004 Free Software Foundation, Inc.GDB is free software, covered by the GNU General Public License, and you arewelcome to change it and/or distribute copies of it under certain conditions.Type "show copying" to see the conditions.There is absolutely no warranty for GDB. Type "show warranty" for details.This GDB was configured as "x86_64-apple-darwin".sharedlibrary apply-load-rules allAttaching to process 43518.When I exit the program unrecognized selector sent to instance I get this error:-------------------------------------------------2010-02-02 21:33:07.054 Temp-Feb1st[43518:207] *** -[Temp_Feb1stViewController applicationWillTerminate:]: unrecognized selector sent to instance 0x3b022302010-02-02 21:33:07.056 Temp-Feb1st[43518:207] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[Temp_Feb1stViewController applicationWillTerminate:]: unrecognized selector sent to instance 0x3b02230'2010-02-02 21:33:07.056 Temp-Feb1st[43518:207] Stack: ( 29307995, 2467386633, 29689915, 29259382, 29112002, 112186, 29040645, 102128, 137480, 2748069, 2769965, 2750163, 2777269, 37404369, 29092736, 29088840, 37398413, 37398610, 2781187, 8620, 8474)killError resetting ObjC debugger mode: The program being debugged was signaled while in a function called from GDB.GDB has restored the context to what it was before the call.To change this behavior use "set unwindonsignal off"Evaluation of the expression containing the function (gdb_objc_endDebuggerMode) will be abandoned.(gdb) The responsible Code:--------------------------@implementation Temp_Feb1stViewController// +--------------------------------------+// ----------------------------| Create File data Path to Memory |---------------------------------// +--------------------------------------+-(NSString *)dataFilePath {NSArray

the Xcode main window but are primarily located in the Debug area, the debug navigator, the breakpoint navigator, and the source editor. The debugging UI is dynamic; it fatal error: unexpectedly found nil while unwrapping an optional value reconfigures as you build and run your app. To customize how Xcode xcode 8 displays portions of the UI, choose Xcode Preferences > Behaviors.The illustration below shows the default layout of the Xcode could not find developer disk image debugger with the app paused at a breakpoint. General NotesHere are a few notes about debugging in general and some basic information about Xcode as you begin to read this http://classroomm.com/objective-c/index.php?topic=2892.0;wap2 chapter.The Five Parts of Debugging and the Debugging ToolsThere are five parts to the debugging workflow:Discover. Identify a problem.Locate. Determine where in the code the problem occurs.Inspect. Examine the control flow and data structures of the running code to find the cause of the problem.Fix. Apply your insight into the cause of the problem to devise a solution, and edit the code https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/debugging_with_xcode/chapters/debugging_tools.html to suit.Confirm. After editing, run the app and check it with the debugger to be sure the fix was successful. The division of labor in these five parts of debugging are not necessarily reflected in the specifics of the debugging tools, although some tools are more pointed at discovery (for instance, the debug gauges), some are particularly useful for dealing with locations of interest in your code (breakpoints), and others are more specific to inspection (the debug area’s variables view and the debug navigator’s process view). Think of the debugging tools as addressing the five parts of debugging more as a function of how you use them. For instance, you use the Quick Look feature to inspect the state of a graphical object as you work through a problem, but you can also think of it as being a discovery tool, using it to see how a complex graphic is “assembled” as you iterate through a set of drawing calls. In other words, how you put a tool to work for you often determines which part of the debugging effort it addresse

Workspace Toolbar Using Multiple Workspace Windows Creating Apps Working with Projects Working with Targets Working on Related Projects Using Alternative Toolchains Writing Code Opening and Adding Files Editing Source Code Search and Replace Working with Symbols Analyzing https://developer.apple.com/library/content/documentation/ToolsLanguages/Conceptual/Xcode_Overview/UsingtheDebugger.html Your Code Customizing the Editor Finding Editor Help Building a User Interface Using Interface Builder Designing with Storyboards Connecting Objects to Code Building for Multiple Screen Sizes Viewing Object Documentation Previewing Your User Interface Creating https://facebook.github.io/react-native/docs/debugging.html and Rendering Custom View Classes Finding Help for Interface Builder Adding Assets Adding Images Adding Particle Emitter Effects Adding 3D Scenes Adding Data Sets Adding Watch Complications Running Your App Building Your App Running in error resetting Simulator Running on a Device Managing Schemes Debugging Using the Debugger Examining the View Hierarchy Examining System Impact Measuring Performance Simulating Problems Customizing Your Workflow Testing Using Unit Tests Using Continuous Integration Testing Using Code Coverage Recording UI Tests Managing Changes Using File Saving Using Undo Using Source Code Control Learning More Getting a Hands-On Introduction Finding Step-by-Step Instructions Learning from Detailed User Guides Staying Up to Date Revision error resetting objc History Document Revision History On This Page Controlling Execution Viewing State Information Finding Memory Corruption Debugging Metal Debugging OpenGL Using the Debugger After you click the Run button in the workspace toolbar and your app builds successfully, Xcode runs your app and starts a debugging session. You can debug your app directly within the source editor with graphical tools such as data tips and Quick Look for the value of variables. The debug area and the debug navigator let you inspect the current state of your running app and control its execution. Creating a quality app requires that you minimize your app’s impact on your users’ systems. Use the debug gauges in the debug navigator to gain insight into your app’s resource consumption, and when you spot a problem, use Instruments to measure and analyze your app’s performance. Use the energy guides to minimize your impact on battery life. For more information, see Energy Efficiency Guide for iOS Apps and Energy Efficiency Guide for Mac Apps. If you are developing an iOS or watchOS app, use Simulator to find major problems during design and early testing. You can configure Xcode to help you focus on your debugging tasks. For example, when your code hits a breakpoint, y

Existing AppsColorsImagesHandling TouchesAnimationsAccessibilityTimersDirect ManipulationDebuggingTestingJavaScript EnvironmentNavigationPerformanceUpgradingPlatform Specific CodeGesture Responder SystemGuides (iOS)Native ModulesNative UI ComponentsLinking LibrariesRunning On DeviceRunning On SimulatorCommunication between native and React NativeGuides (Android)Native ModulesNative UI ComponentsRunning On DeviceGenerating Signed APKProfiling Android UI PerformanceBuilding React Native from sourcecomponentsActivityIndicatorActivityIndicatorIOSDatePickerIOSDrawerLayoutAndroidImageKeyboardAvoidingViewListViewMapViewModalNavigatorNavigatorIOSPickerPickerIOSProgressBarAndroidProgressViewIOSRefreshControlScrollViewSegmentedControlIOSSliderSliderIOSStatusBarSnapshotViewIOSSwitchSwitchAndroidSwitchIOSTabBarIOSTabBarIOS.ItemTextTextInputToolbarAndroidTouchableHighlightTouchableNativeFeedbackTouchableOpacityTouchableWithoutFeedbackViewViewPagerAndroidWebViewapisActionSheetIOSAdSupportIOSAlertAlertIOSAnimatedAppRegistryAppStateAsyncStorageBackAndroidCameraRollClipboardDatePickerAndroidDimensionsEasingGeolocationImageEditorImagePickerIOSImageStoreIntentAndroidInteractionManagerLayoutAnimationLinkingNativeMethodsMixinNativeModulesNetInfoPanResponderPermissionsAndroidPixelRatioPushNotificationIOSSettingsStatusBarIOSStyleSheetSystraceTimePickerAndroidToastAndroidVibrationVibrationIOSLayout PropsShadow PropsDebugging #Accessing the In-App Developer Menu #You can access the developer menu by shaking your device or by selecting "Shake Gesture" inside the Hardware menu in the iOS Simulator. You can also use the Command⌘ + D keyboard shortcut when your app is running in the iPhone Simulator, or Command⌘ + M when running in an Android emulator.The Developer Menu is disabled in release (production) builds.Reloading JavaScript #Instead of recompiling your app every time you make a change, you can reload your app's JavaScript code instantly. To do so, select "Reload" from the Developer Menu. You can also press Command⌘ + R in the iOS Simulator, or press R twice on Android emulators.If the Command⌘ + R keyboard shortcut does not seem to reload the iOS Simulator, go to the Hardware menu, select Keyboard, and make sure that "Connect Hardware Keyboard" is checked.Automatic reloading #You can speed up your development times by having your app reload automatically any time your code changes. Automatic reloading can be enabled by selecting "Enable Live Reload" from the Developer Menu.You may even go a step further and keep your app running as new versions of your files are injected into the JavaScr