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 catch the crash, but the crash stack is empty #250
Comments
I get the same issue. |
I meet the same problem. Anyone fix it? |
I meet the same problem, but why? |
How to reproduce the problem? |
KSCrash set the cursor imageAddress to 0 in function kssymbolicator_symbolicate() when parsing the symbol table without Debugging Symbols(Xcode --> build settings --> Strip Style -- >Debugging Symbols) |
I meet the same problem. Anyone fix it? |
All three reports issue author provided are related to C++ exceptions. Has anyone received non-C++-crashes without backtrace? |
I'll take a look at this problem next week |
If meet the empty stack for C++ exception, can find the reason on this issue. #205 |
Sorry, it would have been better to say "next month". |
@chzhij5 老哥,你们用的是哪个版本的ks?1.15.8? |
Hi! We investigated the problem and possible solutions in our team. There is one: During installation process of KSCrashMonitor_CPPException we can use a "hack" that is described and implemented in https://github.com/facebook/fishhook. It allows hooking any call of dynamically linked binary's function. So we hook If any library has a weak symbol The only problem that can't be solved is if some binary has strong @kstenerud, what do you think? We've read your post at stackoverflow, and it seems that the idea above may solve it, at least partially. We can go ahead and create a pull-request where fishhook will be a dependancy of KSCrash(or KSCrash subspec like i.e. 'KSCrash/Recording/ImprovedCPPExceptionsHandling`). |
We actually can call |
That sounds good, we will have a try next week in our in-house app. |
Here the PR: #375 |
I get some crash report from our user, but I found that some of the crash stack is empty.
These are some of the raw json crash report.
1.txt
2.txt
3.txt
The text was updated successfully, but these errors were encountered: