Comment 2 for bug 1321679

I’m seeing a different backtrace when commenting out a few tests (thus getting some tests to pass):

Program received signal SIGSEGV, Segmentation fault.
0xb6f0baa8 in __memcpy_neon () at ../ports/sysdeps/arm/armv7/multiarch/memcpy_impl.S:332
332 ../ports/sysdeps/arm/armv7/multiarch/memcpy_impl.S: No such file or directory.
(gdb) bt
#0 0xb6f0baa8 in __memcpy_neon () at ../ports/sysdeps/arm/armv7/multiarch/memcpy_impl.S:332
#1 0xb6564892 in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/arm-linux-gnueabihf/bits/string3.h:51
#2 QString::append (this=this@entry=0xbeffe538, str=...) at tools/qstring.cpp:8695
#3 0xb6144122 in operator+= (s=..., this=0xbeffe538) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qstring.h:411
#4 QV4::StringPrototype::method_replace (ctx=<optimized out>) at jsruntime/qv4stringobject.cpp:593
#5 0xb613024e in QV4::BuiltinFunction::call (that=<optimized out>, callData=<optimized out>) at jsruntime/qv4functionobject.cpp:583
#6 0xb6164c68 in call (d=0xaff01eb0, this=<optimized out>) at jsruntime/qv4object_p.h:270
#7 QV4::Runtime::callProperty (context=0xbeffe7c0, name=..., callData=...) at jsruntime/qv4runtime.cpp:938
#8 0xaba068dc in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)