Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F flatpak-qt-creator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Marco Bubke
  • flatpak-qt-creator
  • Repository
  • flatpak-qt-creator
  • src
  • plugins
  • debugger
  • gdb
  • gdbengine.cpp
Find file Blame History Permalink
  • hjk's avatar
    Debugger: Always check for availability of python with GDB · c7ea186d
    hjk authored Jun 03, 2013
    
    
    Trying to avoid that round-trip on versions that are known to
    not have it puts us on the mercy of detecting the version,
    which is unreliable by nature, and bad in practice, as proven
    by the recent MinGW builds.
    
    Change-Id: I122eb03fe0ddcb193ed8d45e672564f7113b662f
    Reviewed-by: default avatarRay Donnelly <mingw.android@gmail.com>
    Reviewed-by: default avatarhjk <hjk121@nokiamail.com>
    c7ea186d