diff options
| author | mread <qt-info@nokia.com> | 2011-10-13 14:54:45 +0100 |
|---|---|---|
| committer | mread <qt-info@nokia.com> | 2011-10-13 15:02:22 +0100 |
| commit | 138b9d7349d5daa1808d8bd891c5ecf817f98c52 (patch) | |
| tree | 4f367f35aa90b9fa89e615e388bd1b909fdd1bad /tools/runonphone/symbianutils/launcher.cpp | |
| parent | fe5f996eac2a4b4e7e704f7cdaebe990a76c6034 (diff) | |
| download | qt4-tools-138b9d7349d5daa1808d8bd891c5ecf817f98c52.tar.gz | |
runonphone timestamps nanosecond formating set to 9 chars, 0 padded
runonphone was dropping leading zeros after the decimal point in its
timestamp formating. For example [123.000456789] was printed as
[123.456789], which is quite a different number.
The formatting now pads the nanoseconds component with leading zeros to
9 characters. Timestamps are now always displayed with a 9 character
nanoseconds component, with leading and trailing zeros as appropriate.
For example:
[1897.070556640] [Qt Message] QEglContext::swapBuffers
Reviewed-by: Shane Kearns
Diffstat (limited to 'tools/runonphone/symbianutils/launcher.cpp')
| -rw-r--r-- | tools/runonphone/symbianutils/launcher.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/runonphone/symbianutils/launcher.cpp b/tools/runonphone/symbianutils/launcher.cpp index ff67881e24..2909696227 100644 --- a/tools/runonphone/symbianutils/launcher.cpp +++ b/tools/runonphone/symbianutils/launcher.cpp @@ -440,7 +440,7 @@ void Launcher::handleResult(const TrkResult &result) quint64 timestamp = extractInt64(result.data) & 0x0FFFFFFFFFFFFFFFULL; quint64 secs = timestamp / 1000000000; quint64 ns = timestamp % 1000000000; - msg = QString("[%1.%2] %3").arg(secs).arg(ns).arg(QString(result.data.mid(8))); + msg = QString("[%1.%2] %3").arg(secs).arg(ns,9,10,QLatin1Char('0')).arg(QString(result.data.mid(8))); logMessage("TEXT TRACE: " + msg); } } else { |