1. 16 Jul, 2016 2 commits
  2. 15 Jul, 2016 3 commits
    • Peifeng Yu's avatar
      Workaround for lldb tty setting on linux · 44e9a143
      Peifeng Yu authored
      44e9a143
    • Peifeng Yu's avatar
    • Peifeng Yu's avatar
      Improve gdb plugin unit tests · 9cb910b9
      Peifeng Yu authored
      Summary:
      This is a side effect of my work on lldb plugin unit tests, in which I tried to fix the somewhat unreliable test results.
      
      - Move unit test debugees to common folder, make gdb uses common unit test helpers
      - Make gdb plugin unit tests more reliable. waitForState now guarantees the session state after returning is exactly the requested one (otherwise fails the test).
      
      The main problem is that DebugSession could end and get deleted when running event loop (i.e. in QTest::qWait).
      And this fix adds proper checks to it. This by itself doesn't fix any tests, but it helps when some tests
      did goes wrong. Without this fix, they could crash the whole test process due to accessing to deleted object.
      
      Test Plan: gdb plugin unit tests (and actually some lldb plugin unit tests, which is only on local yet)
      
      Reviewers: #kdevelop, apol, kfunk
      
      Reviewed By: #kdevelop, apol, kfunk
      
      Subscribers: kfunk, kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D1985
      9cb910b9
  3. 14 Jul, 2016 4 commits
    • Peifeng Yu's avatar
      Cleanup MIDebugger output signals · 6d7a4cfe
      Peifeng Yu authored
      Summary:
      There are 4 signals used for various output from the debugger:
      - applicationOutput: emitted when got stream record from the 'target' channel
      - userCommandOutput: emitted when got stream record from the 'console' channel and it's a user command
      - internalCommandOutput: emitted when got stream record from the 'console' channel and it's not a user command
      - internalOutput: emitted when got stream record from the 'log' channel or stderr from the debugger
      
      And there are 2 output toolviews when debugging.
      - The normal Debug Output panel controled by MIDebugJob
          * Shows applicationOutput, via MIDebugSession::inferiorOutputLines
          * Shows internalCommandOutput, via MIDebugSession::debuggerInternalCommandOutput
      - The GDBOutputWidget which is part of the GDB plugin
          * Shows userCommandOutput, via MIDebugSession::debuggerUserCommandOutput
          * Shows internalCommandOutput, via MIDebugSession::debuggerInternalCommandOutput
          * Shows internalOutput, via MIDebugSession::debuggerInternalOutput
      
      This should match the old behavior for toolviews and fixes the testStdOut unit test.
      
      Test Plan: gdb unit tests
      
      Reviewers: #kdevelop, apol
      
      Reviewed By: #kdevelop, apol
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D2175
      6d7a4cfe
    • Kevin Funk's avatar
      Make compile · 38e82245
      Kevin Funk authored
      CCMAIL: rjvbertin@gmail.com
      38e82245
    • René J.V. Bertin's avatar
      support -iframework and -F header search path options · 46c0ea43
      René J.V. Bertin authored
      REVIEW: 128272
      46c0ea43
    • Peifeng Yu's avatar
      77ef011a
  4. 13 Jul, 2016 11 commits
  5. 12 Jul, 2016 10 commits
  6. 11 Jul, 2016 7 commits
  7. 10 Jul, 2016 3 commits