qt5base-lts

History

Edward Welbourne c066656aff Avoid read-outside-array error by QStringRef over-reach Constructing a QStringRef directly from the string, offset and a length is UB if the offset + length exceeds the string's length. Thanks to Robert Loehning and libFuzzer for finding this. QString::midRef (as correctly used in both changed uses of QStringRef, since `432d3b6962`) takes care of that for us. Changed one UB case and a matching but correct case, for consistency. In the process, deduplicate a QStringList look-up. Added tests to exercise the code (but the one that exercises the formerly UB case doesn't crash before the fix, so isn't very useful; the invalid read is only outside the array it's scanning, not outside allocated memory). Change-Id: I7051bbbc0267dd7ec0a8f75eee2034d0b7eb75a2 Reviewed-by: Anton Kudryavtsev <antkudr@mail.ru> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2019-02-08 13:56:25 +00:00
..
auto	Avoid read-outside-array error by QStringRef over-reach	2019-02-08 13:56:25 +00:00
baselineserver	Fix compilation	2018-12-03 07:53:00 +00:00
benchmarks	Add testlib selftests for double and for non-finite float and double	2019-02-06 10:11:22 +00:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	macOS: Only do gamma-corrected blending for subpixel-antialiased text	2018-12-23 12:00:07 +00:00
shared	tests: Include QFileInfo in emulationdetector.h	2018-05-14 12:36:28 +00:00
testserver	Rework QNetworkReply tests to use docker-based test servers	2018-07-27 17:40:27 +00:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	Build examples and tests only if their requirements are met	2017-03-22 15:55:55 +00:00

README

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.