-
-
Notifications
You must be signed in to change notification settings - Fork 341
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KSCrash dependency crashing #136
Comments
Can you please add some more information. |
Cocoapods. I believe the issue is that when dispatch_queue_ptr is NULL attempting to dereference with *dispatch_queue_ptr is causing a crash. from Podfile.lock
|
Same here, this is the most common crash in our app too. :( Versions we are using, from our Cartfile.resolved:
|
hey can you guys try to update to KSCrash |
Thank you @HazAT, will update this in the next rls. |
@HazAT You need to update https://github.com/getsentry/sentry-swift/blob/master/Cartfile and set the version to |
@JagCesar it's in master now but I guess I need to make a new release |
@HazAT We're submitting an update to the App Store on Thursday, could you plz create a new release asap so we can get this issue fixed? |
@JagCesar done ... I had to change the kscrash dependency to my fork because there was a misconfig in the header files (thats also the reason why it took so long). |
@HazAT Thank you! :) A minor thing would be to move your fork of KSCrash to the "getsentry" organisation instead of having it on your own private user. No need to do it right now, but would be great if you can do this for the next release. Keep up the good work! |
@JagCesar will send a PR to KSCrash ... this is just temporary |
Thank you so much! |
This is my #1 crash right now.
in KSThread.c, EXC_BAD_ACCESS
-->if(dispatch_queue_ptr == NULL || idInfo->thread_handle == 0 || *dispatch_queue_ptr == NULL)
{
KSLOG_TRACE("This thread doesn't have a dispatch queue attached : %p", thread);
return false;
}
Crashed: Thread
0 KSCrash 0x10056738c ksthread_getQueueName (KSThread.c:82)
1 KSCrash 0x100567370 ksthread_getQueueName (KSThread.c:75)
2 KSCrash 0x10053f6c8 monitorCachedData (KSCrashCachedData.c:84)
3 libsystem_pthread.dylib 0x18d021850 + 240
4 libsystem_pthread.dylib 0x18d021760 _pthread_start + 282
5 libsystem_pthread.dylib 0x18d01ed94 thread_start + 4
The text was updated successfully, but these errors were encountered: