1. 04 Jul, 2016 1 commit
  2. 29 Jan, 2016 1 commit
  3. 19 Jan, 2016 1 commit
  4. 16 Jan, 2015 1 commit
  5. 09 Oct, 2014 1 commit
  6. 16 Jul, 2014 1 commit
  7. 08 Jan, 2014 1 commit
  8. 26 Jun, 2013 1 commit
  9. 08 Mar, 2013 2 commits
  10. 01 Feb, 2013 1 commit
  11. 16 Jan, 2013 1 commit
  12. 22 Oct, 2012 1 commit
  13. 09 Oct, 2012 1 commit
  14. 08 Oct, 2012 1 commit
    • Nikolai Kosjar's avatar
      CrashHandler: Add "Attach and Debug" button. · e186f9b2
      Nikolai Kosjar authored
      This will launch a new instance of Qt Creator attaching to the crashed
      instance.
      
      The 'Restart' functionality is now represented as a check box since it
      would be confusing to have one button that restarts the app and quits
      the crash handler and another one that starts a debugger but keeps the
      crash handler open (which is necessary, otherwise the crashed app will
      quit).
      
      Change-Id: Id88f418ff73ab7bc72b05753ce2b61bbef8f30cf
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@digia.com>
      e186f9b2
  15. 21 Sep, 2012 1 commit
    • Nikolai Kosjar's avatar
      Linux: Add a crash handler providing a backtrace for debug builds. · 903281b3
      Nikolai Kosjar authored
      Use case: You're working with a debug version of Qt Creator and you're
      interested in getting a backtrace displayed as soon as Qt Creator
      crashes without searching for the core file, starting your debugger, ...
      
      Once a 'serious signal' (currently SIGILL, SIGFPE, SIGSEGV, SIGBUS,
      SIGPIPE) is delivered, a popup displays the following debug information:
      
       - Qt Creator version (same as in the about dialog)
       - Kernel version (uname -a)
       - GNU/Linux Distribution (/etc/lsb-release)
       - Backtrace (by gdb)
      
      Please note that this crash handler is built and used only in debug mode
      on GNU/Linux. It's solely meant as a convenience tool for the developer.
      
      In contrast to the breakpad integration, this crash handler operates
      'offline'. There is no network i/o involved.
      
      Change-Id: Idcfb1bf1ad68942615ecfe0dffc0d03154455049
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@digia.com>
      Reviewed-by: default avatarhjk <qthjk@ovi.com>
      903281b3