1. 12 Dec, 2020 1 commit
    • Christoph Roick's avatar
      Modify DBus service name to allow using QDBusServiceWatcher · 243461e9
      Christoph Roick authored
      Fix the DBus connection which allows passing a debuggee to one of the
      KDevelop debuggers for future versions (>=5.7) of KDevelop. Instead of the
      deprecated serviceOwnerChanged signal, a QDBusServiceWatcher is used,
      which requires a different naming scheme. See KDevelop commit 69ef7ea8.
      This change has no impact on the connection with current versions of KDevelop.
  2. 21 Sep, 2020 1 commit
  3. 12 Jul, 2019 1 commit
  4. 25 Jan, 2019 1 commit
    • Christoph Roick's avatar
      Request change of ptrace scope from KCrash · 9f3cfcff
      Christoph Roick authored
      - On Linux recent kernels only allow attaching a debugger
        to a process if
        * the right to attach to processes is enabled system-wide
        * the debugger is an ancestor of the debuggee
        * or the debuggee sets a tracer process by a call to
          `prctl(PR_SET_PTRACER, debugger_pid, 0, 0, 0);`
      - DrKonqi will ask the debuggee by a socket connection to
        set a new ptracer. This is required if an external debugger
        is started (using the usually hidden Debug button).
      - When the debugger has finished, the access is requested back
        to DrKonqi to allow internal backtraces again.
      Test Plan:
      - try to attach gdb or KDevelop to the process by
        using the Debug button: operation will not be permitted
      - apply corresponding patches to KCrash D11236 and DrKonqi
      - the process can now be debugged
      - after detaching the debugger again, a backtrace can be
        created using the DrKonqi dialog as usual
      Reviewers: #plasma_workspaces, #frameworks, ossi
      Reviewed By: ossi
      Subscribers: ossi, lepagevalleeemmanuel, maximilianocuria, adridg, plasma-devel
      Tags: #plasma
      Differential Revision: https://phabricator.kde.org/D11235
  5. 11 Mar, 2018 1 commit
  6. 06 Mar, 2018 2 commits
    • Christoph Roick's avatar
      DrKonqi: Enable DBus-Interface for debugging with KDevelop · 2c0f0449
      Christoph Roick authored
      - register a DBus service to make it work at all
      - service name unique by debuggee pid
      - switch hierarchy of adaptor and launcher
        - a single adaptor keeps track of multiple launchers
        - the debugger should provide a unique identification
      - only works with a corresponding patch in KDevelop
      Test Plan:
      - apply KDevelop patch D10196 and start a new KDevelop session "test"
      - enable the DrKonqi debug button
      - enable ptrace
      - start a kde program (kate for instance)
      - start "drkonqi --dialog --appname kate --pid xxxx"
      - check Debug options: gdb, KDevelop (GDB) - test, KDevelop (LLDB) - test
      - start another KDevelop session "test2" -> additional debug options are now available
      - end session "test2" -> additional options vanished again
      - select "KDevelop (GDB) - test" -> KDevelop raises, DrKonqi buttons are disabled
      - use the GDB console to detach the process and end GDB
      - DrKonqi buttons are reenabled again
      Reviewers: #kdevelop, #plasma_workspaces, mwolff
      Reviewed By: #kdevelop, mwolff
      Subscribers: mwolff, ngraham, plasma-devel
      Tags: #plasma
      Differential Revision: https://phabricator.kde.org/D10195
    • Christoph Roick's avatar
  7. 07 Feb, 2018 1 commit
  8. 16 Jan, 2018 1 commit
  9. 01 Nov, 2015 1 commit
  10. 20 Oct, 2014 2 commits
  11. 08 Apr, 2014 1 commit
    • Aleix Pol Gonzalez's avatar
      Initial import from the monolithic kde-runtime. · 81c1985e
      Aleix Pol Gonzalez authored
      This is the beginning of revision history for this module. If you
      want to look at revision history older than this, please refer to the
      techbase wiki for how to use Git history grafting. At the time of
      writing, this wiki is located here:
      If you have already performed the grafting and you don't see any
      history beyond this commit, try running "git log" with the "--follow"
      Branched from the monolithic repo kde-runtime, frameworks  branch, at commit