Merge pull request #9 from mer-qt/mer-logging

Mer logging
Logging: support %{time} and %{time format} in QT_MESSAGE_PATTERN

[ChangeLog][QtCore][Logging] QT_MESSAGE_PATTERN can include a
timestamp using %{time} or %{time format}

Change-Id: I2aaa9c7a6fcb340b5ce9f1fe8a78002e5fc4e6fe
Reviewed-by: Gunnar Sletta <gunnar.sletta@jollamobile.com>
Fix typo in 'time' message pattern.

Change-Id: I3f3861a0307aad9d5bb92c0fdeb719950aa370c8
Merge pull request #10 from sletta/mer-stable

[qtbase] Logging: support %{time} and %{time format} in QT_MESSAGE_PATTERN
Do not try to handle OOM exceptions in logging

We duplicate quite some code here in an attempt to still print
messages, even in OOM situations. However, we've in general given up
on handling OOM exceptions gracefully in Qt: On modern systems
you hardly reach the point of not being able to allocate (smaller)
chunks in the first place, since the system will usually overcommit,
or bring the system to halt by heavy paging.

In 7cafb62538661863e5c we removed already similar logic in QDebug
class.

Change-Id: I4f84641c41c5e230a60dc0b7a5b0a13dec20f90f
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Merge pull request #11 from sletta/mer-stable

[qtdeclarative] Do not try to handle OOM exceptions in logging
More logging
Support CLOCK_BOOTTIME in QElapsedTimer.

CLOCK_MONOTONIC does not include time spent in suspend, which is particularly
problematic on e.g. Android systems, which suspend often. CLOCK_BOOTTIME was
introduced in Linux 2.6.39 addressing exactly this problem: it is identical to
CLOCK_MONOTONIC, but also includes time spent in suspend.

Unfortunately, due to a kernel bug, CLOCK_BOOTIME can also go backwards
sometimes. Identify this happening, and abort() - while also providing a tunable
to set the default clock type.

Change-Id: I679e788cbe3ae2a2d5be59ed99427678f09cc032