Comment 1 for bug 1321679

The failure is actually a segfault, here is the backtrace I managed to get (running the tests on a chromebook):

********* Start testing of QmlTests *********
Config: Using QtTest library 5.3.0, Qt 5.3.0
PASS : QmlTests::AddressBar::initTestCase()

Program received signal SIGSEGV, Segmentation fault.
QV4::StringPrototype::method_split (ctx=<optimized out>) at jsruntime/qv4scopedvalue_p.h:313
313 jsruntime/qv4scopedvalue_p.h: No such file or directory.
(gdb) bt
#0 QV4::StringPrototype::method_split (ctx=<optimized out>) at jsruntime/qv4scopedvalue_p.h:313
#1 0xb613024e in QV4::BuiltinFunction::call (that=<optimized out>, callData=<optimized out>) at jsruntime/qv4functionobject.cpp:583
#2 0xb6164c68 in call (d=0xaff020e8, this=<optimized out>) at jsruntime/qv4object_p.h:270
#3 QV4::Runtime::callProperty (context=0xbeffe678, name=..., callData=...) at jsruntime/qv4runtime.cpp:938
#4 0xafacb0ba in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)