-
Notifications
You must be signed in to change notification settings - Fork 0
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
A bug in running dev.sh #1
Comments
Process: Chili [98106] Date/Time: 2014-10-06 17:44:32.005 +0300 Sleep/Wake UUID: A90CEA88-E9B1-41EB-81F2-AA9206821C15 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) VM Regions Near 0: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2:: Dispatch queue: com.apple.libdispatch-manager Thread 3: Thread 4: Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 2 Binary Images: External Modification Summary: VM Region Summary: REGION TYPE VIRTUAL |
(bug posted on wrong repo: https://github.com/bbonf/chili) fixed here: https://github.com/bbonf/chili/commit/b1d0de81209c7085358be6adef9181c3f2fb2b25 |
6/10/14 17:44:28.367 ibtoold[98100]: CGSConnectionByID: 0 is not a valid connection ID.
6/10/14 17:44:31.974 Chili[98106]: applicationDidFinishLaunching_
6/10/14 17:44:32.007 ReportCrash[98107]: Env var utf8 null at argbuf position 131: ù
6/10/14 17:44:32.007 ReportCrash[98107]: Env var utf8 null at argbuf position 395: ù
6/10/14 17:44:32.008 ReportCrash[98107]: Env var utf8 null at argbuf position 1019: ù
6/10/14 17:44:32.008 ReportCrash[98107]: Env var utf8 null at argbuf position 1048: ù
6/10/14 17:44:32.008 ReportCrash[98107]: Env var utf8 null at argbuf position 1177: ù
6/10/14 17:44:32.009 ReportCrash[98107]: Env var utf8 null at argbuf position 1528: ù
6/10/14 17:44:32.009 ReportCrash[98107]: Env var utf8 null at argbuf position 1666: ù
6/10/14 17:44:32.611 ReportCrash[98107]: Saved crash report for Chili[98106] version 0.0.1 (0.0.1) to /Users/gilad/Library/Logs/DiagnosticReports/Chili_2014-10-06-174432_G-MBP.crash
The text was updated successfully, but these errors were encountered: