qt-creator

Files

hjk 4f36713716 Debugger: Explicitly handle uint8_t and int8_t

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>

2013-10-10 21:25:36 +02:00

deep/deep

Merge remote-tracking branch 'origin/2.6'

2013-01-31 16:25:33 +01:00

README

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

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

simple_test_app.cpp

Debugger: Explicitly handle uint8_t and int8_t

2013-10-10 21:25:36 +02:00

simple_test_app.pro

Merge remote-tracking branch 'origin/2.7'

2013-03-28 12:19:45 +01:00

simple_test_plugin.cpp

Incremented year in copyright info

2013-01-29 16:27:03 +01:00

simple_test_plugin.pro

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

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

simple.pro

debugger: move defines to a .pro file that is actually looked at

2012-02-28 12:01:35 +01: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)