Status: New
Owner: ----

New issue 1265 by [email protected]: Occasional segfaults on ARM from revision 7252.
http://code.google.com/p/v8/issues/detail?id=1265

I have not investigated the bug yet.

Occasional segfaults can be observed on ARM from revision 7252. (r7251 and before look fine.)

I can observe the bug on actual hardware (Tegra2) with a release shell. (I could not observe the bug on the Simulator)
I narrowed it down to r7252 checking the mjsunit/escape.js test:

./shell.7252 --stress-opt --always-opt test/mjsunit/mjsunit.js test/mjsunit/escape.js

The frequency of the bug appearing is about 1/5.
Here is a backtrace (release shell compiled with additional debug symbols):

(gdb) run
Starting program: /home/ubuntu/aleram/bleeding_edge/shell.7252.g --stress-opt --always-opt test/mjsunit/mjsunit.js test/mjsunit/escape.js
[Thread debugging using libthread_db enabled]
============ Stress 1/5 ============
[New Thread 0x42b2f460 (LWP 31370)]
============ Stress 2/5 ============
============ Stress 3/5 ============
============ Stress 4/5 ============

Program received signal SIGSEGV, Segmentation fault.
0x0009ab22 in v8::internal::Map::CopyDropDescriptors() ()
(gdb) bt
#0  0x0009ab22 in v8::internal::Map::CopyDropDescriptors() ()
#1 0x00034b38 in v8::internal::Factory::CopyMapDropDescriptors (src=...) at src/factory.cc:283 #2 0x0001e780 in v8::internal::Genesis::CreateEmptyFunction (this=0xbed95454) at src/bootstrapper.cc:513 #3 0x0001ef8a in Genesis (this=0xbed95454, global_object=..., global_template=..., extensions=<value optimized out>) at src/bootstrapper.cc:2071 #4 0x0001f0b0 in v8::internal::Bootstrapper::CreateEnvironment (global_object=<value optimized out>, global_template=<value optimized out>, extensions=0x0) at src/bootstrapper.cc:320 #5 0x00019826 in v8::Context::New (extensions=0x0, global_template=..., global_object=...) at src/api.cc:3468
#6  0x0000aae6 in RunMain(int, char**) ()
#7  0x0000aae6 in RunMain(int, char**) ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)


Alexandre

--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev

Reply via email to