Closed Bug 507081 Opened 16 years ago Closed 12 years ago

Fennec failed at startup with "Illegal Instruction" on ARM9(v5) platform (TI Davinci 6446)

Categories

(Core :: JavaScript Engine, defect)

Other
Linux
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: nishad.p, Unassigned)

Details

(Whiteboard: [mobile])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.37 Safari/530.5 Build Identifier: Fennec B2 We had dowloaded Fennec B2 from http://haqq.ws/mozilla/mc.bundle.2009.09.02 and updated it. While cross compiling, we used the mozconfig as shown: xxxxxxxxxxxxxxxxxxxxxxxxx mozconfig xxxxxxxxxxxxxxxxxxxxxxxxxxx ac_add_options --host=arm-linux PATH=$PATH:$xprefix/bin env CROSS_LIB_PATH="${xprefix}/lib:${xprefix}/usr/lib" CROSS_COMPILE=1 HOST_LIBIDL_CONFIG=/usr/bin/libIDL-config-2 LIBIDL_CONFIG=$xprefix/usr/bin/libIDL-config-2 # Options for client.mk. mk_add_options MOZ_BUILD_PROJECTS="xulrunner mobile" mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../mobilebase # Global options -- uncomment these lines for debug version ac_add_options --enable-debug ac_add_options --disable-optimize ac_add_options --disable-xpcom-obsolete ac_add_options --disable-xpcom-fastload # XULRunner options ac_add_app_options xulrunner --prefix=/home/nishad/fennec_cross/install/ ac_add_app_options xulrunner --enable-application=xulrunner ac_add_app_options xulrunner --disable-javaxpcom # Enabling --with-arm-kuser implies Linux on ARM and enables # kernel optimizations for that platform ac_add_app_options xulrunner --with-arm-kuser ac_add_app_options xulrunner --enable-system-cairo ac_add_options --enable-default-toolkit=cairo-gtk2 # Disabling tests due to bug 454881 ac_add_options --disable-tests #ac_add_options --disable-jemalloc # mobile options ac_add_app_options mobile --enable-application=mobile ac_add_app_options mobile --with-libxul-sdk=../xulrunner/dist xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx While running the binary on our platform we get an "Illegal Instruction" and the application didnt start. With gdb we get the following error message: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (gdb) r Starting program: /home/nishad/fennec_b2/fennec [Thread debugging using libthread_db enabled] [New Thread 0x4001f570 (LWP 893)] [New Thread 0x42eff490 (LWP 896)] [New Thread 0x436ff490 (LWP 897)] [New Thread 0x43fff490 (LWP 898)] [New Thread 0x44bff490 (LWP 899)] [Thread 0x44bff490 (LWP 899) exited] [New Thread 0x44bff490 (LWP 900)] [New Thread 0x454ff490 (LWP 901)] [Thread 0x454ff490 (LWP 901) exited] Program received signal SIGILL, Illegal instruction. [Switching to Thread 0x4001f570 (LWP 893)] 0x425adf04 in ?? () xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Our platform: TI Davinci 6446 (ARM9) OS: Montavista Linux Pro 4.0.1 Library version: arm gcc: 4.2.2 gtk: 2.14 Processor Speed: 298MHz RAM: 250MB We also tried Fennec B1 with updated patches till 24 July. There we got a "Segmantation Fault". It didnt even start execution coz we had give a print statement in the main() with dint happen. 1) Is this issue due to the TI Davinci Platform (ARM9)? 2) Is it due to configuration options given form building the source? 3) Is it due to the limitation in RAM or CPU cycles? 4) Will Fennec run on ARM9 or ARM v5? Reproducible: Always
Reporter, is this still occurring on the latest beta?
I also experience this on but on a Vortex processor. I am currently searching for the cause.
FYI, I disabled javascript.options.jit.chrome and the browser came up fine. I think they broke something in this version of tracemonkey. ref. https://wiki.mozilla.org/JavaScript:TraceMonkey Hope it works for you guys.
According to comment 3, this seems like a bug in javascript code, so moving it to that component.
Assignee: nobody → general
Component: Linux/Maemo → JavaScript Engine
Product: Fennec → Core
QA Contact: maemo-linux → general
Whiteboard: [mobile]
I assume this bug has been since addressed.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.