debugging crash logs - iphone

I have the following crash logs:
I am unsure my self, why this is happening. Any pointers? I think it has to do with blocks

Related

having issues with "dfx start" and "dfx deploy" code

Does anyone know the solution to this? I am new to this and learning. I am on Macbook Air m1.
This is the end code while running dfx start in the terminal:
thread 'replica-actor' panicked at 'called Result::unwrap() on an Err value: Cannot start the replica: Timeout', src/dfx/src/actors/replica.rs:279:78
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
This is what happens while running dfx deploy in terminal:
Error: An error happened during communication with the replica: error sending request for url (http://127.0.0.1:8000/api/v2/status): error trying to connect: tcp connect error: Connection refused (os error 61)
Does anyone know anything about this?
Found the solution to the problem. I was running the code while it was stored in an external drive. When I created the same folder on my desktop and ran everything the same way, the problem got solved and I no longer have those errors in my terminal. I don't know how it is happening, but I just discovered it right now.
Try "dfx start --emulator"

Swift Unified Logging

I was searching for some information on how to do proper logging in swift. I found Unified Logging: https://developer.apple.com/documentation/os/logging.
When trying it, I couldn't figure out how I can see the logs for only my defined Subsystem and the Category. Is there a way in the console oder the system log of the ios simulator to have only the application related logs? I couldn't see the app logs neither in the console nor in the simulator's system logs.
Here is my code:
let customLogger = OSLog(subsystem: "com.myapp", category: "CustomLogs")
os_log("Test log message.", log: customLogger, type: .debug)
In case you still looking for an answer.

Debug Assertion Failed in mfc140ud

I use vs2015. When I run my program in debug mode this debug assertion failed happend.
Anyone knows how to deal with it?
Release mode is OK.
Thank you for your replys. I think the mainly reason is the socket workthread sendmessage to close the socket itself in a multi-thread application.

Couldn't register com.xxx.appname with the bootstrap server. Error: unknown error code.Program received signal: “SIGABRT”

I am getting this error while running in device.
Couldn't register com.xxxx.appname with the bootstrap server.
Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.Program received signal: “SIGABRT”.
Now i rectified this problem .I have posted answer also if anyone got this error follow my post..
Try this,
Deleteing the app, restarting Xcode, clean build, didn't do anything
--> restart your computer
--> restart the phone

NSZombie Enabled, MallocStackLogging

I am testing an EXE_BAD_ACCESS error. I have set NSZombieEnabled, MallocStackLogging, MallocStackLoggingNoCompact to YES. now in the debugger I get this message when I run my app in the debug mode from the device I could see this:
iota(3586) malloc: recording malloc stacks to disk using standard recorder
iota(3586) malloc: stack logs being written into /private/var/mobile/Applications/8E21A85B-369E-4487-962B-1550E56602DC/tmp/stack-logs.3586.iota.index
iota(3586) malloc: Please issue: cp /private/var/mobile/Applications/8E21A85B-369E-4487-962B-1550E56602DC/tmp/stack-logs.3586.iota.suRQjy.link /tmp/
and when I am about to hit the error I get,
2011-02-14 14:29:44.350 iota[3586:307] *** -[CFString autorelease]: message sent to deallocated instance 0x81eab70
Finally when I give the command in debugger to see the stack trace
(gdb) shell malloc_history 3586 0x81eab70
I get
malloc_history cannot examine process 3586 because the process does not exist.
Can anyone tell me what I am doing wrong, before the error is about the occur , I set
set env MallocStackLogging 1 in the debugger too
Thanks in Advance
You might not be able to look at the malloc_history because you're running this on the device. I had the same error and Instruments was also freezing or not starting my application.
But - if I ran in the iOS simulator and then configured the allocations tool to handle zombies (this option wasn't available on the device) then I can see pretty quickly the object which was prematurely released.
From what I understand you are releasing manually a string that is already on the autorelease Pool.
All strings created with
[NSString stringWithFormat:#"some %#", #"text"];
And
[NSString stringWithString:#"some text"];
must not be manually released.