b7b11c8095
As the comment says, on most RISC platforms, the return address need not be on the stack in the first place. In fact, in all ones currently supported by Qt, it's passed in a register to the callee, which has the option of simply saving it in a callee-save register when calling leaf functions. Even if it is using a frame pointer, the compiler can simply use any register. That means unwinding the stack is not possible in the absence of either debug information or stack-unwind information, neither of which backtrace(3) will use. Strictly speaking, even on x86 the compiler can use the RBP register for any purpose and thus make getting the backtrace() impossible, but in practice it seems to work. Fixes: QTBUG-121389 Change-Id: I5dd50a1a7ca5424d9e7afffd17acbd01ef916f5d Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io> (cherry picked from commit 03f1ea3dcb956c69216084d1df3a21f460c8475b) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.