<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>223721</bug_id>
          
          <creation_ts>2021-03-24 18:39:53 -0700</creation_ts>
          <short_desc>webkitgtk2.28.0 jsc crash on start [MIPS64el]</short_desc>
          <delta_ts>2022-02-15 07:48:41 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>WebKitGTK</component>
          <version>WebKit Local Build</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>221198</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Critical</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="zpcheng">chengzhpchn</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>bugs-noreply</cc>
    
    <cc>mcatanzaro</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1743633</commentid>
    <comment_count>0</comment_count>
    <who name="zpcheng">chengzhpchn</who>
    <bug_when>2021-03-24 18:39:53 -0700</bug_when>
    <thetext>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) &quot;jsc&quot; 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)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1744048</commentid>
    <comment_count>1</comment_count>
    <who name="zpcheng">chengzhpchn</who>
    <bug_when>2021-03-25 20:14:40 -0700</bug_when>
    <thetext>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!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1841713</commentid>
    <comment_count>2</comment_count>
    <who name="Michael Catanzaro">mcatanzaro</who>
    <bug_when>2022-02-15 07:47:51 -0800</bug_when>
    <thetext>This was fixed via bug #221198.

I&apos;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 ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1841715</commentid>
    <comment_count>3</comment_count>
    <who name="Michael Catanzaro">mcatanzaro</who>
    <bug_when>2022-02-15 07:48:41 -0800</bug_when>
    <thetext>(In reply to Michael Catanzaro from comment #2)
&gt; I&apos;m not sure why your backtrace is so poor. :( I understand having only two
&gt; frames makes it basically impossible to debug....

Bug #233949 should help with that.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>