diff options
author | Milian Wolff <milian.wolff@kdab.com> | 2018-01-30 15:10:18 +0100 |
---|---|---|
committer | Ulf Hermann <ulf.hermann@qt.io> | 2019-05-03 12:41:07 +0000 |
commit | b5df17c04718ddc995ddf9030754253e8d4a0ca8 (patch) | |
tree | ebfc547c6c7dda2fdf08a35c5f0410ee931fc2df /app | |
parent | 9ba708cca62ca704b4048fb49de1431aa19fdcd7 (diff) |
Support (null) as address in kallsyms
Apparently some kallsyms report the obfuscated address as (null)
instead of all-zero. Handle this scenario instead of giving up
parsing the file.
Change-Id: I108c20d1845933a429ee5cd26217b707f6aac4cc
Reviewed-by: Milian Wolff <milian.wolff@kdab.com>
Diffstat (limited to 'app')
-rw-r--r-- | app/perfkallsyms.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/app/perfkallsyms.cpp b/app/perfkallsyms.cpp index 84b8847..1a64cbd 100644 --- a/app/perfkallsyms.cpp +++ b/app/perfkallsyms.cpp @@ -53,7 +53,7 @@ bool PerfKallsyms::parseMapping(const QString &path) bool ok = false; entry.address = address.toULongLong(&ok, 16); - if (!ok) { + if (!ok && address != "(null)") { m_errorString = tr("Invalid address: %1").arg(QString::fromUtf8(address)); valid = false; break; |