Closed Bug 922529 Opened 12 years ago Closed 10 years ago

Intermittent PROCESS-CRASH | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | application crashed [@ js::PropDesc::initialize(JSContext*, JS::Value const&, bool)]

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: cbook, Unassigned)

References

(
URL
)

Details

(Keywords: crash, intermittent-failure)

Crash Data

Android 4.0 Panda mozilla-inbound opt test mochitest-8 on 2013-10-01 00:21:47 PDT for push eedf61cab3fa slave: panda-0618 https://tbpl.mozilla.org/php/getParsedLog.php?id=28600135&tree=Mozilla-Inbound PROCESS-CRASH | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | application crashed [@ js::PropDesc::initialize(JSContext*, JS::Value const&, bool)] 00:34:09 WARNING - PROCESS-CRASH | /tests/js/xpconnect/tests/mochitest/test_sameOriginPolicy.html | application crashed [@ js::PropDesc::initialize(JSContext*, JS::Value const&, bool)] 00:34:09 INFO - Crash dump filename: /tmp/tmpcSvplY/63e55975-9e44-0881-2658ad96-7e274995.dmp 00:34:09 INFO - Operating system: Android 00:34:09 INFO - 0.0.0 Linux 3.2.0+ #2 SMP PREEMPT Thu Nov 29 08:06:57 EST 2012 armv7l pandaboard/pandaboard/pandaboard:4.0.4/IMM76I/5:eng/test-keys 00:34:09 INFO - CPU: arm 00:34:09 INFO - 2 CPUs 00:34:09 INFO - Crash reason: SIGILL 00:34:09 INFO - Crash address: 0x63421c02 00:34:09 INFO - Thread 13 (crashed) 00:34:09 INFO - 0 libxul.so!js::PropDesc::initialize(JSContext*, JS::Value const&, bool) [jscntxt.h:eedf61cab3fa : 670 + 0x2] 00:34:09 INFO - r4 = 0x6c21d270 r5 = 0x5d41a1a0 r6 = 0x63c25f80 r7 = 0x5d41a1a0 00:34:09 INFO - r8 = 0x0000ffff r9 = 0x00000001 r10 = 0x665c79e0 fp = 0xffffff87 00:34:09 INFO - sp = 0x5d41a100 lr = 0x63437d15 pc = 0x63421c02 00:34:09 INFO - Found by: given as instruction pointer in context 00:34:09 INFO - 1 libxul.so!ParsePropertyDescriptorObject [jsproxy.cpp:eedf61cab3fa : 669 + 0xb] 00:34:09 INFO - r4 = 0x5d41a1c8 r5 = 0x5d41a208 r6 = 0x6c21d270 r7 = 0x5d41a1a0 00:34:09 INFO - r8 = 0x5d41a260 r9 = 0x5d41a34c r10 = 0x00000000 fp = 0x5d41a1a0 00:34:09 INFO - sp = 0x5d41a150 pc = 0x63437d15 00:34:09 INFO - Found by: call frame info 00:34:09 INFO - 2 libxul.so!js::Proxy::defineProperty(JSContext*, JS::Handle<JSObject*>, JS::Handle<int>, JS::Handle<JS::Value>) [jsproxy.cpp:eedf61cab3fa : 2360 + 0x3] 00:34:09 INFO - r4 = 0x00000000 r5 = 0xffffff82 r6 = 0x6c21d270 r7 = 0x5d41a34c 00:34:09 INFO - r8 = 0x5d41a350 r9 = 0x5d41a260 r10 = 0x6c21d270 fp = 0x5d41a350 00:34:09 INFO - sp = 0x5d41a1f8 pc = 0x63438061 00:34:09 INFO - Found by: call frame info 00:34:09 INFO - 3 libxul.so!js::DefineProperty(JSContext*, JS::Handle<JSObject*>, JS::Handle<int>, js::PropDesc const&, bool, bool*) [jsobj.cpp:eedf61cab3fa : 948 + 0x3] 00:34:09 INFO - r4 = 0x665c79e0 r5 = 0xffffff87 r6 = 0x5d41a34c r7 = 0x63436455 00:34:09 INFO - r8 = 0x00000001 r9 = 0x5d41a2e8 r10 = 0x6c21d270 fp = 0x5d41a350 00:34:09 INFO - sp = 0x5d41a248 pc = 0x63425abd 00:34:09 INFO - Found by: call frame info 00:34:09 INFO - 4 libxul.so!js::DefineOwnProperty(JSContext*, JS::Handle<JSObject*>, JS::Handle<int>, JS::Handle<JS::Value>, bool*) [jsobj.cpp:eedf61cab3fa : 966 + 0x13] 00:34:09 INFO - r4 = 0x00000001 r5 = 0x5d41a298 r6 = 0x6c21d270 r7 = 0x5d41a2e8 00:34:09 INFO - r8 = 0x5d41a3c0 r9 = 0x5d41a350 r10 = 0x5d41a34c fp = 0x5d41a2e8 00:34:09 INFO - sp = 0x5d41a290 pc = 0x63425c1b 00:34:09 INFO - Found by: call frame info 00:34:09 INFO - 5 libxul.so!obj_defineProperty [Object.cpp:eedf61cab3fa : 846 + 0xf] 00:34:09 INFO - r4 = 0x5d41a34b r5 = 0x63c25f80 r6 = 0x00000003 r7 = 0x6c21d270 00:34:09 INFO - r8 = 0x0000000f r9 = 0x6cccf580 r10 = 0x6635b580 fp = 0x5d41a3c8 00:34:09 INFO - sp = 0x5d41a340 pc = 0x6337c3ef 00:34:09 INFO - Found by: call frame info 00:34:09 INFO - 6 0x6a90fe86
Can I get the crash dump for this file? SIGILL is really weird. I'd like to get a dump of the machine code around the crash address (a hundred or so bytes above and below the crash address would be great).
Inactive; closing (see bug 1180138).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.