User Agent: Mozilla/4.0 (compatible; MSIE 8.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: [B2G version] Helix V1.1.0 hd [repo steps] 1.Doing the MMI test; 2.Test BT connnection; 3.Test sensor normal; Actual results: B2G reset. Expected results: B2G normal.
From kernel log,the error is : ... 01-06 04:05:36 <7>[176, b2g] [ 111.411266] b2g: unhandled page fault (11) at 0x00000000, code 0x017 ... arroding to the PC(0x41202e42), in dump log is the thread of libxul.so crashed,as following: ... Thread 0 (crashed) 0 libxul.so + 0x622e42 r4 = 0x4b5a7ec0 r5 = 0x00000000 r6 = 0xbea197e0 r7 = 0x00000001 r8 = 0xbea1980f r9 = 0x40307c6c r10 = 0x00000000 fp = 0x00000000 sp = 0xbea19790 lr = 0x410d87c3 pc = 0x41202e42 ... Could you give us some message about libxul.so.
Please note https://bugzilla.mozilla.org/show_bug.cgi?id=938953#c2 (In reply to lecky from comment #2) > 01-06 04:05:36 <7>[176, b2g] [ 111.411266] b2g: unhandled page fault (11) > Could you give us some message about libxul.so. No, we cannot. We don't have your symbols and your codes. You have to parse your dmp file with your symbols, and do the analysis.
Please see the file of dmp_result in attachment at comment 1.There is our parse dump result with our symbols.
Flags: needinfo?(lecky.wanglei) → needinfo?(ahuang)
(In reply to lecky from comment #4) > Please see the file of dmp_result in attachment at comment 1.There is our > parse dump result with our symbols. Lecky, Did you really see it yourself first? It's just wasting every developer's time if you Lecky guys keep handling bugs like this. No matter POVB bugs or not. Please stop using shared bugzilla account and don't ni me from now on. Please be responsible and sensible to bugs you report on bugzilla, and please do things make sense to analyze your bugs. Wayne, We really need certain actions to stop the people of Lecky from wasting developers' resources. This bug is not the first one during the past six months.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.