<br>On Monday, October 26, 2015, Atul Sowani <<a href="mailto:sowania@us.ibm.com">sowania@us.ibm.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif">I am trying to port PhantomJS 2.0.1
to IBM PPC64LE platform. PhantomJS uses qtwebkit version 153112 and I am
facing a few crashes in the JavaScript interpreter code. I was directed
to this forum by PhantomJS developers to get help/insight about the interpreter.</font></blockquote><div><br></div><div>That WebKit revision is more than two years old: <a href="http://trac.webkit.org/changeset/153112">http://trac.webkit.org/changeset/153112</a></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif">Requesting this forum admins/contributors
to confirm if this is the right forum to discuss JS interpreter issues,
and is it mandatory to open a bug report in order to discuss it on this
mailing list.</font><br></blockquote><div><br></div>Can you reproduce the same interpreter crash on Mac or GTK+ if you built trunk WebKit? (You can export JSC_useJIT=0 in env to disable JIT)<div><br></div><div>If not, can reproduce the crash on Mac/GTK+ ports at r153112? If you can, you can probably binary search the revision that fixed the crash.</div><div><div><br></div><div>- R. Niwa<br><div> </div></div></div><br><br>-- <br>- R. Niwa<br>