User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba; .NET4.0C; .NET4.0E; Tablet PC 2.0) Steps to reproduce: [probability] low, about 5% [repro steps] USB connected, running monkey test Actual results: Actual results: During monkey test, screen freezed and no response during monkey test Expected results: Expected results: During monkey test, there is no abnormal. After Monkey test, the device still can work well. [Question] Once freeze happened, how to collect the useful logs and efficient debug methods?
There is no information indicating this being a different problem than bug 908610. And no valid debugging information here. Duping
Comment 2 has logs from reporter sent in an email. Alan, if you can check or ask someone that can if you'd be absent. Thanks
The log doesn't indicate crash and can't show us what main thread and other IO thread are doing. Hi Lecky, As our talk in August, please attach gdb and provide all b2g threads' back trace if you met a frozen screen. (The command should be "thread apply all bt")
ok, I will try the method you mentioned