Yes, it's is a bug in libqt5script5: (gdb) break QTJSC::Heap::markConservatively(QTJSC::MarkStack&, void*, void*) Breakpoint 1 at 0xf65219c0: file ../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp, line 791. (gdb) r The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /home/dave/debian/qbs/qbs-1.12.2+dfsg/bin/qbs build --settings-dir qbsres/settings -f /home/dave/debian/qbs/qbs-1.12.2+dfsg/qbs.qbs -d qbsres -p 'qbs resources' project.withCode:false project.withDocumentation:false profile:none [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/hppa-linux-gnu/libthread_db.so.1". [New Thread 0xef7e7440 (LWP 1788)] [New Thread 0xee582440 (LWP 1789)] Restoring build graph from disk [Detaching after fork from child process 1790] [New Thread 0xedd81440 (LWP 1791)] [Thread 0xee582440 (LWP 1789) exited] Building for configuration default [Switching to Thread 0xedd81440 (LWP 1791)]
Thread 4 "QThread" hit Breakpoint 1, QTJSC::Heap::markConservatively ( this=0xf8b53c78, markStack=..., start=0xed5826c8, end=0xedd81000) at ../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp:791 791 ../3rdparty/javascriptcore/JavaScriptCore/runtime/Collector.cpp: No such file or directory. The address 0xedd81000 is the end of the stack. Dave -- John David Anglin dave.ang...@bell.net