Recent versions of GDB seem to require 'make install' to find their
Python bits. Given that this is not really an option, check the
usual suspects, too.
Change-Id: I5217c0184681d4a86992fe0b8989498843b26cea
Reviewed-by: David Schulz <david.schulz@digia.com>
Reviewed-by: hjk <hjk121@nokiamail.com>
The type reported by LLDB for Qt 4 is actually wrong, but the type is
irrelevant for the dumper itself anyhow.
Change-Id: I33002316fa72cc8501f26dcc3ee08675547841ae
Reviewed-by: hjk <hjk121@nokiamail.com>
The previous workaround for the Qt 4 optimized int,uint,short,ushort
QHashNode wasn't working for the QHashNode dumper itself because of
unknown key type. Instead we first try to find the 'key' child directly,
if that fails we look for it in the second child (which would be the
anonymous union from the optimized hash node, which contains the key).
Also fix the expected type for QHashNode in the optimized case for Qt4
Change-Id: Ib48c2c0afec081ff38cd750c3d515a5e678e9661
Reviewed-by: hjk <hjk121@nokiamail.com>
The GDB case is still wrong, but it the data GDB produces.
Change-Id: I97c656a666b98da2f62b354b5d1c699301d67b23
Reviewed-by: hjk <hjk121@nokiamail.com>
This is now (additionally) on a per-entry level, resulting
in less duplication.
Change-Id: Ia93547396384fe5b421c4b601b52476a23cdfa89
Reviewed-by: hjk <hjk121@nokiamail.com>
Make it work with LLDB, show simple values always directly.
Change-Id: I463ef81183792f85243d679dee69a41db00bed07
Reviewed-by: hjk <hjk121@nokiamail.com>
Dumper was working, but the default constructor doesn't do
the parsing already nowadays.
Change-Id: I098b0a03ad7d994b5746f3a4a6c39d29133509b0
Reviewed-by: hjk <hjk121@nokiamail.com>
Would be nicer if there was a global way to tell GDB to not produce
"adorned" output...
Task-number: QTCREATORBUG-10344
Change-Id: I5355ebea0570f76415fdacfed34e1311825f57b9
Reviewed-by: André Hartmann <aha_1980@gmx.de>
Reviewed-by: hjk <hjk121@nokiamail.com>
QStringList is movable in Qt 5.
Task-number: QTCREATORBUG-10211
Change-Id: I6b94acd37bbf8ca165960c50fd3da81408ccbb1b
Reviewed-by: David Schulz <david.schulz@digia.com>
- Don't remove temp stuff when QTC_KEEP_TEMP_FOR_TEST is set, even
if the test passes.
- Heed QTC_USE_GLIBCXXDEBUG_FOR_TEST to enforce compilation with
-D_GLIBCXX_DEBUG to trigger a way to test the full-debug version
of g++'s standard library
Change-Id: I5bf9f423835883349af3ce772e900e0a2123c69e
Reviewed-by: David Schulz <david.schulz@digia.com>
Do it in code. Relying on the environment variable breaks in
too many cases (remote; unmodified project; ...) to be useful.
Change-Id: I67577fef22942d75d32d356f38c4ff0c752fe157
Reviewed-by: hjk <hjk121@nokiamail.com>
Access to the is_shared flag seems somewhat indeterministic
across platforms/compilers. Hard-code to non-shared for now.
Change-Id: Iaac9dd8fcee28ffd1e599300a1c12f3215823573
Reviewed-by: hjk <hjk121@nokiamail.com>
They were only showing the integral parts in the
summary line. Duh...
Change-Id: I5efd7a9d5b7bfd6ffd68dcda824c95dd7a7a52b0
Reviewed-by: hjk <hjk121@nokiamail.com>
It's generally not too useful to see it at all, and in cases of
'const int' vs 'int const' it just defeats the test's purpose.
Change-Id: I3439dd8fcee28ffd1e599300a1c12f3215823573
Reviewed-by: hjk <hjk121@nokiamail.com>
