Bug 223721 – webkitgtk2.28.0 jsc crash on start [MIPS64el]

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: WebKitGTK

[zpcheng]

I compiled jsc and libJavaScriptCore.so on UOS Linux [LOONGSON / MIPS64el] platform, but the jsc crash on start, however, the stack trace shown by gdb is too short to make any help:

Program received signal SIGABRT, Aborted.
0x00007ffff4e85d60 in raise () from /lib/mips64el-linux-gnuabi64/libc.so.6
(gdb) info thread
  Id   Target Id                             Frame
* 1    Thread 0x7ffff5a84ce0 (LWP 8298) "jsc" 0x00007ffff4e85d60 in raise ()
(gdb) bt
#0 0x00007ffff4e85d60 in raise () from /lib/mips64el-linux-gnuabi64/libc.so.6
#1 0x00007ffff4e51608 in abort () from /lib/mips64el-linux-gnuabi64/libc.so.6
Backtrace stopped: frame did not save the PC

of course I tried the latest stable release, it crashed also.
and I run TestWTF to check more information:
webkitgtk2.28.0 -- run ok with some failed cases;
webkitgtk2.30.5 -- crash with 2 failed cases (Hasher.cpp:138, 155)

[zpcheng]

in PageBlock.h defines :
constexpr size_t CeilingOnPageSize = 4 * KB;
for MIPS64el, this value shall be adjust to 16 * KB

the assertion check in PageBlock.cpp leads to the crash.
I think a more clear hint message will be appreciated!

[Michael Catanzaro]

This was fixed via bug #221198.

I'm not sure why your backtrace is so poor. :( I understand having only two frames makes it basically impossible to debug....

*** This bug has been marked as a duplicate of bug 221198 ***

[Michael Catanzaro]

(In reply to Michael Catanzaro from comment #2)
> I'm not sure why your backtrace is so poor. :( I understand having only two
> frames makes it basically impossible to debug....

Bug #233949 should help with that.