-
Notifications
You must be signed in to change notification settings - Fork 402
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
崩溃 #29
Comments
请问 Xcode 的控制台有没有打印出什么具体的 crash 信息呢?
…------------------ 原始邮件 ------------------
发件人: "Jinlongning"<[email protected]>;
发送时间: 2020年6月10日(星期三) 下午2:39
收件人: "QMUI/LookinServer"<[email protected]>;
抄送: "Subscribed"<[email protected]>;
主题: [QMUI/LookinServer] 崩溃 (#29)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Xcode控制台没有打印 crash 信息。 |
额,没有报错信息的话…现在只能看出来是 crash 在了 _markIVarsOfObject:class: 方法里。
有三个调试办法:
1)在 Crash 的时候看看能不能定位到具体报错是在哪一行代码
2)按照 https://lookin.work/faq/integration-sourcecode/ 的指引把 LookinServer 的源代码加到你的工程里,然后在 Xcode 里添加 All Exceptions Breakpoint,试试能不能捕捉到 crash 具体在哪一行
3)你构造一个可以重现该 crash 的 demo 项目发给我(不过这个可能有点难)
…------------------ 原始邮件 ------------------
发件人: "Jinlongning"<[email protected]>;
发送时间: 2020年6月10日(星期三) 下午5:27
收件人: "QMUI/LookinServer"<[email protected]>;
抄送: "471633877"<[email protected]>;"Comment"<[email protected]>;
主题: Re: [QMUI/LookinServer] 崩溃 (#29)
请问 Xcode 的控制台有没有打印出什么具体的 crash 信息呢?
…
------------------ 原始邮件 ------------------ 发件人: "Jinlongning"<[email protected]>; 发送时间: 2020年6月10日(星期三) 下午2:39 收件人: "QMUI/LookinServer"<[email protected]>; 抄送: "Subscribed"<[email protected]>; 主题: [QMUI/LookinServer] 崩溃 (#29) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
Xcode控制台没有打印信息。
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: