Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-32958

Crash when added empty deploy step

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P1: Critical
    • 4.8.6, 5.2.0
    • 5.0.0
    • Core: Other
    • None
    • MacOS X 10.8
    • c8d9b17367cfdcb034d11f8a168ca4ae3993e7c3 764f1a51209212b6fc60cef5c12e9748d06b57de

    Description

      1. Select "Projects"
      2. Select "Run" settings
      3. Click on "Add deploy step" - "Custom Process Step"
      4. Leave the fields empty - don't enter anything for the Custom process step
      5. Try to start the application. It crashes with the following back trace:
      (lldb) bt

      • thread #1: tid = 0x1c03, 0x0000000100cfbf36 QtCore`QProcessPrivate::waitForStarted(int) + 102, stop reason = EXC_BAD_INSTRUCTION (code=12, subcode=0x0)
        frame #0: 0x0000000100cfbf36 QtCore`QProcessPrivate::waitForStarted(int) + 102
        frame #1: 0x0000000100cb59b8 QtCore`QProcess::waitForStarted(int) + 24
        frame #2: 0x000000010d957334 libProjectExplorer_debug.dylib`ProjectExplorer::AbstractProcessStep::run(this=0x0000000116cce2f0, fi=0x0000000115fa29c8) + 1076 at abstractprocessstep.cpp:207
        frame #3: 0x000000010d953de8

      Attachments

        Issue Links

          replaces

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-33021 QProcess::waitForStarted crashes if start() failed early

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; Flaky tests; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-33158 Crash in (QProcess (). waitForStarted ())

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; Flaky tests; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              stromme Christian
              neterror Plamen Todorov
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes