qt-creator

Files

hjk 2244e2b26c Debugger: Use direct memory instead of member access

This introduces a dumper types abstraction layer with classes
Dumper.{Value,Type,Field} wrapping either gdb.{Value,Type,Field}
or lldb.{SBValue,SBType,SBField} and uses it to move
to more direct memory accesses in the dumper implementation.

This way we can use duck typing for artificial intermediate
objects eliminating the need for {gdb.Value,lldb.SBValue}.cast()
in some case which are flaky in general and typically not
available in release builds.

As consequence QRegion and QVariant dumper work without debug
info now.

Change-Id: Iea2411175ef67f2bf651ee7eaade9879ed5ceba1
Reviewed-by: Christian Stenger <christian.stenger@qt.io>

2016-09-14 12:38:45 +00:00

deep/deep

Update License according to agreement with Free Qt Foundation

2016-01-19 16:01:06 +00:00

README

debugger: rename manual tests from 'gdbdebugger' to 'debugger'

2011-08-24 13:54:34 +02:00

simple_test_app.cpp

Debugger: Use direct memory instead of member access

2016-09-14 12:38:45 +00:00

simple_test_app.pro

enable c++11 really globally

2016-08-02 07:52:38 +00:00

simple_test_plugin.cpp

Update License according to agreement with Free Qt Foundation

2016-01-19 16:01:06 +00:00

simple_test_plugin.pro

Nuke plugins PROVIDER settings

2014-05-08 15:29:11 +02:00

simple.pro

Debugger: Make manual tests compilable on OSX

2016-03-16 09:20:52 +00:00

README

Thinks to check:

- loading of custom dumpers (as seen on QByteArray/QString)
- availability of Qt debug information (custom display of QObject derived
class)
- availabitily of Qt sources (single step into some Qt *._cpp_ file)
- setting of breakpoints on dynamically loaded plugins (try plugin.cpp here, especially in constructors)
- check I/O  (qDebug, std::cout, std::cerr)